Edgewall Software

Opened 16 years ago

Last modified 7 years ago

#3003 new enhancement

milestone could be a ticket

Reported by: ThurnerRupert Owned by:
Priority: normal Milestone: unscheduled
Component: ticket system Version: 0.9.4
Severity: normal Keywords: tracobject
Cc: Haipisporah Branch:
Release Notes:
API Changes:
Internal Changes:


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 (0)

Change History (19)

comment:1 by anonymous, 16 years ago

Component: timelineroadmap
Owner: changed from Jonas Borgström to Christopher Lenz

comment:2 by anonymous, 16 years ago

Component: roadmapticket system
Owner: changed from Christopher Lenz to Jonas Borgström

comment:3 by Christian Boos, 16 years ago

Keywords: tracobject added
Owner: changed from Jonas Borgström to Christian Boos

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.

comment:4 by Christian Boos, 15 years ago

Milestone: 2.0

Long term topic.

comment:5 by Emmanuel Blot, 14 years ago

#6594 has been marked as a duplicate.

comment:6 by Haipisporah, 13 years ago

Cc: Haipisporah added
Milestone: 2.0
Version: 0.9.4

Hi People How are you doing?

comment:7 by Remy Blank, 13 years ago

Milestone: 2.0
Version: 0.9.4

comment:8 by Christian Boos, 12 years ago

Milestone: 2.0unscheduled

Milestone 2.0 deleted

comment:9 by tiger_seed <tiger_seed@…>, 11 years ago

comment:10 by Christian Boos, 11 years ago

Strange, "tiger_seed" was not part of the content submitted to the SpamFilter.

comment:11 by Dirk Stöcker, 11 years ago

Fixed in r10541.

comment:12 by Christian Boos, 11 years ago

Great! Thanks, all 0.12 and 0.13 instances were upgraded.

comment:13 by Christian Boos, 11 years ago

(so long, tiger_seed ;-) )

comment:14 by Remy Blank, 11 years ago

Mmh… Comment numbering seems to be thoroughly fscked up here. I wonder how we managed to get comment:2 after comment:8

comment:15 by Christian Boos, 11 years ago

Definitely a ticket full of interesting [OT] issues ;-)

The second comment:2 was created by a batch modification at the occasion of the deletion of the temporary triaging milestone. That looks like the culprit.

comment:16 by Christian Boos, 11 years ago

Same story on #4583 (also the same two consecutive milestone deletion there), but on #7342 it's fine, and there has been one change between those two milestone deletion.

comment:17 by Remy Blank, 11 years ago

OT: I'm currently in the process of fixing all those comment numbering issues by hand in the database. I have tried reproducing the issue with current 0.12-stable, but wasn't able to. My guess is that the milestone deletion was done at a point where we still had issues with comment numbering (#8947), but the timing doesn't seem right. If anyone can find a reliable way to reproduce the issue, I'm interested.

comment:18 by framay <franz.mayer@…>, 10 years ago

On-Topic again:

By making milestone a ticket, it would also solve #7871. But I guess changing milestone to ticket is quite a lot of work (described at SubTickets). And it would depend on #886 (#31 is a more generic version of that ticket).

comment:19 by Ryan J Ollos, 7 years ago

Owner: Christian Boos removed

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.