Not only with "versions" but also with "components"

[anonymous]

Hi all,

I think this plugin would be very useful with "components". It would be good to add some options to the code to manage "components" in the same way the plugin manage "versions".

Thanks.

Ed.

[Lucas Rangit MAGASWERAN]

We're probably using components differently so I may be confused. Are you asking that components and milestones also be associated with versions?

[Malcolm Studd]

I think he means make another plugin that makes components visible the way this plugin makes versions visible. I.e. component pages where you can edit the description, add new components, and wiki links to components. That way you aren't limited to the admin page for components. It's a good idea, but not one I think I'll find any time to work on.

[Ryan J Ollos]

Replying to mestudd:

I think he means make another plugin that makes components visible the way this plugin makes versions visible. I.e. component pages where you can edit the description, add new components, and wiki links to components. That way you aren't limited to the admin page for components. It's a good idea, but not one I think I'll find any time to work on.

​t:#1233, which I'll be working on for inclusion in Trac 1.2, will expose the components' descriptions and owners through a macro, and display them on a wiki page that will be linked from the ticket page. ​t:#3911 has the goal of making the Component a first-class object in Trac, as the reporter here is requesting.

I feel it is outside the scope of the ExtendedVersionPlugin. The ideas are all good, but they will significantly expand the scope of this plugin, and I won't find time to work on it. If I do work on it, it will probably be for direct inclusion in the Trac core. ​t:PatchWelcome though!