On Jun 5, 10:14 am, Brettschneider Falk <fbrettschnei...@baumer.com> wrote: > This would also solve the problem that on ticket creation people often ask > what they should type in ticket fields 'version' and 'milestone', and what > the difference is. Since every Trac milestone has a version here, I explain > it as version="seen in version" and milestone="scheduled to be closed with > version". But that doesn't explain why both ticket fields offer different > sets of choices. > For our needs I'm thinking about reflecting the 'version' table also on the > roadmap page, either handling them as own dates or as properties of dates. > Maybe there is a good wiki page explaining the backgrounds of why the data > model is as it is today.
Read your post a bit closer and found out that we had the same problem. We solved it by using the Component MilestoneToVersion (see [1]). IMHO version is different from milestone: version indicates the version number where the bug occured and milestone is the target version (when the target milestone has been finished it will be a version). HTH, Franz [1] http://trac.edgewall.org/browser/trunk/sample-plugins/milestone_to_version.py -- 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.
