Edgewall Software

Ticket #3003 (new enhancement)

Opened 2 years ago

Last modified 4 months ago

milestone could be a ticket

Reported by: ThurnerRupert Owned by: cboos
Priority: normal Milestone: 2.0
Component: ticket system Version: 0.9.4
Severity: normal Keywords: tracobject
Cc:

Description

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?

Attachments

Change History

Changed 2 years ago by anonymous

  • owner changed from jonas to cmlenz
  • component changed from timeline to roadmap

Changed 2 years ago by anonymous

  • owner changed from cmlenz to jonas
  • component changed from roadmap to ticket system

Changed 2 years ago by cboos

  • keywords tracobject added
  • owner changed from jonas to 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.

Changed 18 months ago by cboos

  • milestone set to 2.0

Long term topic.

Changed 4 months ago by eblot

#6594 has been marked as a duplicate.

Add/Change #3003 (milestone could be a ticket)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.