More than one version field in tickets

[Daniel Cantarín]

Hi there.

I would like to have a functionality added to track, i guess it should be done through this plugin and not as a core functionality, and would like to know your opinion about it.

Currently, trac allows to set a "version" field to a given ticket. I would like to have two: a version of ocurrence of a ticket, and a version scheduled to be fixed.

For example: in early development (let's say, version 0.1.0) there are lots of known bugs or tickets related to incomplete functionalities, that are NOT planed to be included in next release (0.2.0), or even planed at all yet (empty "version to be fixed" field).

We're using our only "version" field for "version of ocurrence", we have milestones that trascend release dates (we DO version releases with incomplete milestones), and we have no way of sorting our tickets to easily handle scheduled releases. We pretend to release every N weeks, order our tickets for future versions, and manage incomplete tickets from version to version (in a similar way milestones do).

So... the way we use "version" as abstraction is very similar to "milestone" (as it is a collection of tickets), but milestones and versions behave different, and neither give the ability for a ticket to be part of more than one. Currently, we handle this in a dirty way (not using milestones as such, but as versions).

What do you think about this?

Thanks

[Ryan J Ollos]

Replying to Canta:

We're using our only "version" field for "version of ocurrence", we have milestones that trascend release dates (we DO version releases with incomplete milestones), and we have no way of sorting our tickets to easily handle scheduled releases. We pretend to release every N weeks, order our tickets for future versions, and manage incomplete tickets from version to version (in a similar way milestones do).

It sounds like a version scheduled to be fixed may just be a submilestone. Why not just add a custom field for version scheduled? Perhaps you are looking for the feature provided by MultiSelectFieldPlugin.

[Daniel Cantarín]

Replying to rjollos:

It sounds like a version scheduled to be fixed may just be a submilestone. Why not just add a custom field for version scheduled? Perhaps you are looking for the feature provided by MultiSelectFieldPlugin.

Yes, i believe we can handle this with a simple custom field. I was not aware of that functionality.

Thank you very much for your fast and kind answer, please feel free to close this ticket. :)