#2454 closed enhancement (fixed)
All ticket entries on the Timeline should show the Summary
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | timeline | Version: | 0.9.1 |
| Severity: | minor | Keywords: | tickettype, traclinks |
| Cc: | m@…, mcarpenter@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Seeing entries on the timeline like this
Ticket #3485 (defect) updated by mcarpenter
isn't really meaningful, even if you can get the summary by mousing over the ticket number. Mousing over every entry is a chore. I don't see why the issue type is more important than the title.
An entry like
Ticket #3485 ("No printer is installed": find the cause) updated by mcarpenter
would be much more useful, even if the Summary does sometimes take up a lot of room. The #999 (Summary) formatting matches the <title> of the ticket's page.
Attachments (1)
Change History (12)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Type: | defect → enhancement |
|---|
comment:3 by , 19 years ago
Hovering over the ticket link will give you the summary in a popup so I don't see any reason for it to directly on the page. Of course adding it only for printouts may possibly be useful, but I don't see printing of a timeline being done very often.
comment:4 by , 19 years ago
| Version: | 0.9.2 → 0.9.1 |
|---|
anonymous wrote:
Hovering over the ticket link will give you the summary in a popup so I don't see any reason for it to directly on the page.
I wrote:
Mousing over every entry is a chore.
To expand on that, on my timeline for my project today I have 30-40 entries for tickets on the timeline. Knowing what the issue about is important to figure out what needs follow up on. Should I be mousing over all 30 ticket links? That seems to be a pain to me.
Attaching patch for this change.
by , 19 years ago
| Attachment: | patch-for-2454.trac-0.9.1.patch added |
|---|
Patch to switch summary and ticket type
comment:5 by , 19 years ago
| Milestone: | → 0.10 |
|---|---|
| Owner: | changed from to |
I think the ticket type should come before the ticket summary. What about:
Ticket #2598 (defect: SQL logic error or missing database when database seems fine) created by dangoor+trac@gmail.com
See also #2070.
comment:6 by , 19 years ago
| Cc: | added |
|---|
comment:7 by , 19 years ago
| Milestone: | 0.10 → 1.0 |
|---|---|
| Severity: | normal → minor |
No consensus on that yet. Post-poning.
comment:8 by , 18 years ago
| Keywords: | traclinks tickettype added |
|---|---|
| Milestone: | 1.0 → 0.11 |
| Resolution: | → fixed |
| Status: | new → closed |
comment:9 by , 11 years ago
| Keywords: | traclinks tickettype → traclinks, tickettype |
|---|
comment:10 by , 11 years ago
| Keywords: | traclink added; traclinks removed |
|---|
comment:11 by , 11 years ago
| Keywords: | traclinks added; traclink removed |
|---|
Also this would make a print out of the timeline more useful.