Provide a 'plugin' resolution

[ilias@…]

many tickets within trac are closed, refering to a plugin.

thus the project should possibly use a "plugin" resolution.

example: #4259

the "worksforme" should refere only to the repository contained functionality.

More precise, the resolution should be 'external.plugin', but 'plugin' with a pointer would be enouth.

[Matthew Good]

I've started a topic on the MailingList for discussing the suggestions here and in #4359: ​http://groups.google.com/group/trac-dev/browse_thread/thread/39f61acef4526dbc/1d9e8471e57f40a1#1d9e8471e57f40a1

I'm closing this ticket to try to limit the discussion of triage-related changes to the MailingList until some concensus has been reached.

[Matthew Good]

Oops, I meant #4259.

[ilias@…]

Sorry, I prefere to keep my (valid) issues within the ticket-system, as to be able to internlink to doc's and other issues during the discussion.

If you decide finally that this 'enhancement' wontfix, then of course you are free to close it.

[Matthew Good]

As I explained on the MailingList topic, "plugin" is not really a valid resolution from Trac's perspective. The fact that there's a plugin available doesn't change that the requested feature has been rejected for addition to the Trac core. So, these tickets should all be closed as "wontfix". Linking to a plugin is helpful to users, but it doesn't qualify as a distinct resolution.

[anonymous]

This is the reason why bugzilla has moved resolution. It means that solution of the ticket is required but it is out of scope of current product. Ticket comments need to include a reference to an external issue that should fix this problem.

[Christian Boos]

Replying to anonymous:

This is the reason why bugzilla has moved resolution.

See #905.