milestone could be a ticket

[ThurnerRupert]

can milestones be implemented as tickets too, just by marking a ticket as milestone? a milestone can depend on other milestones, they can be in parallel, they have a responsible, they have an importance, and they depend on the completion of tickets.

currently the milestone concept has a few weaknesses:

• changes are not tracked
• no responsible
• no dependencies (or just implicit by setting dates)
• consolidated view over multiple trac instances, i.e. have a big milestone consisting of small ones stored in other trac instances.

mark a ticket as a milestone, intertrac, and ticket dependencies would solve 95% of these issues. do you see any disadvantage in doing this?

[cboos]

You may want to have a look at SubTickets, which is a special case for the general TracObjectModelProposal approach, and discusses what could be put in common between tickets and milestones.

[cboos]

Long term topic.

[eblot]

#6594 has been marked as a duplicate.