Edgewall Software

Ticket #449 (closed enhancement: fixed)

Opened 4 years ago

Last modified 13 months ago

Link from tickets to milestones

Reported by: cmlenz Owned by: cboos
Priority: normal Milestone: 0.11
Component: ticket system Version:
Severity: normal Keywords:
Cc: somekool@…, m@…, garyo@…

Description

If a ticket has a milestone yet, the milestone name should be a link the the corresponding milestone page of the roadmap, if the remote user has MILESTONE_VIEW perms.

Attachments

Change History

Changed 4 years ago by cmlenz

  • milestone 0.8 deleted

Nice to have but not essential, I guess. Later.

Changed 4 years ago by cmlenz

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

Changed 4 years ago by cmlenz

  • status changed from new to closed
  • resolution set to duplicate

Superseded by #832 which has a broader scope.

Changed 4 years ago by cmlenz

  • status changed from closed to reopened
  • resolution duplicate deleted

Actually, there's a difference between this ticket and #832. Note though that the two requests conflict with each other.

Changed 3 years ago by vittorio

  • severity changed from trivial to enhancement

Changed 3 years ago by cboos

  • owner changed from jonas to cboos
  • status changed from reopened to new

Changed 3 years ago by cboos

  • status changed from new to assigned
  • milestone set to 1.0

#1810 (marked as duplicate) proposes to also create links inside ticket changes, e.g.

milestone set to 1.0

Changed 3 years ago by mgood

#2155 has been marked as a duplicate of this ticket.

Changed 3 years ago by cboos

  • status changed from assigned to new

Note though that the two requests (i.e. this one and #832) conflict with each other.

What about this: as a milestone exist as a Trac object, one would expect to end up on the page corresponding to that object when clicking on its reference...

OTOH, components and versions are not (yet) Trac objects, so clicking on them could lead to some query (e.g. the other tickets having the same component or version, ... but would that be helpful?).

In the end, if there must be a choice, I'd favor the approach presented here rather than the one of #832.

(unaccepting the ticket, as I've not started working on that)

Changed 3 years ago by anonymous

  • cc somekool@… added

Changed 2 years ago by cboos

  • milestone changed from 1.0 to 0.11

#990 and #3547 are also duplicate requests for this feature. I wonder if it's not already implemented in the WorkFlow sandbox.

Changed 23 months ago by Markus Tacker <m@…>

  • cc m@… added
  • version devel deleted

Changed 22 months ago by anonymous

  • cc garyo@… added

Can't just change cc due to akismet without some other text, so I'll just let you know that I would really like to see this. It's simple, but since all the ticket fields are in a loop now, it needs a bit more than the half hour of massaging I could give it...

Changed 19 months ago by cboos

  • priority changed from low to normal

#4538 was closed as duplicate.

Changed 16 months ago by direvus@…

+1. This isn't just "nice to have", it's also "strange not to have". Most everything else in Trac is fabulously interlinked, and then we have this little oddity.

Changed 15 months ago by sbriney@…

I also think that this would be a very useful feature. I am always trying to get from a ticket, back to its Milestone.

Changed 15 months ago by cboos

  • status changed from new to assigned

Done in r5479 (in the FieldRefactoring branch)

Changed 13 months ago by cboos

  • status changed from assigned to closed
  • resolution set to fixed
  • milestone changed from 0.11.1 to 0.11

Ported to trunk in r5813.

Add/Change #449 (Link from tickets to milestones)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.