Hi, RjOllos wrote: > The way my team uses Trac, milestones and versions don't map 1:1. > We may generate multiple versions in the course of a milestone. > > Have you looked at the ExtendedVersionPlugin? > > http://trac-hacks.org/wiki/ExtendedVersionPlugin No, I didn't know it, thanks for the hint.
Looking at its wiki page, it looks as if it sets a 1:n relationship between version and milestone; as if several milestone dates can happen until a version date is reached so to speak. Here we have the case that we have more versions than milestones, each milestone is archived in an internal software version, sometimes there are more than one (=release candidates) versions until a milestone, and we also have several bugfix release versions after the last milestone. And for every version we need to work on some tickets that needs to be shown as progress bar. You see in the end all events are dates where some of them are milestones, and all of them are versions here though I can imagine also dates without a version, and a milestone may be without a new software version. Is ExtendedVersionPlugin suitable for such world? CU, F@lk ---- Falk Brettschneider R&D Software Baumer Optronic GmbH www.baumer.com Gesch?ftsf?hrer: Marcel Seeber * Dr. Oliver Vietze Sitz der Gesellschaft: Radeberg Amtsgericht Dresden: HRB 15379 Ust. ID: DE 189714583 -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
