Ticket #449 (closed enhancement: fixed)
Opened 8 years ago
Last modified 5 years 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@… | ||
| Release Notes: | |||
| API Changes: | |||
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
comment:1 Changed 7 years ago by cmlenz
- Milestone 0.8 deleted
comment:2 Changed 7 years ago by cmlenz
- Component changed from roadmap to ticket system
- Owner changed from cmlenz to jonas
comment:3 Changed 7 years ago by cmlenz
- Resolution set to duplicate
- Status changed from new to closed
Superseded by #832 which has a broader scope.
comment:4 Changed 7 years ago by cmlenz
- Resolution duplicate deleted
- Status changed from closed to reopened
Actually, there's a difference between this ticket and #832. Note though that the two requests conflict with each other.
comment:5 Changed 7 years ago by vittorio
- Severity changed from trivial to enhancement
comment:6 Changed 7 years ago by cboos
- Owner changed from jonas to cboos
- Status changed from reopened to new
comment:7 Changed 7 years ago by cboos
- Milestone set to 1.0
- Status changed from new to assigned
comment:8 Changed 6 years ago by mgood
#2155 has been marked as a duplicate of this ticket.
comment:9 Changed 6 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)
comment:10 Changed 6 years ago by anonymous
- Cc somekool@… added
comment:11 Changed 6 years ago by cboos
- Milestone changed from 1.0 to 0.11
comment:12 Changed 5 years ago by Markus Tacker <m@…>
- Cc m@… added
- Version devel deleted
comment:13 Changed 5 years 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...
comment:14 Changed 5 years ago by cboos
- Priority changed from low to normal
#4538 was closed as duplicate.
comment:15 Changed 5 years 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.
comment:16 Changed 5 years 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.
comment:17 Changed 5 years ago by cboos
- Status changed from new to assigned
Done in r5479 (in the FieldRefactoring branch)
comment:18 Changed 5 years ago by cboos
- Milestone changed from 0.11.1 to 0.11
- Resolution set to fixed
- Status changed from assigned to closed
Ported to trunk in r5813.
Nice to have but not essential, I guess. Later.