Opened 20 years ago
Last modified 3 years ago
#991 new defect
Timeline Ticket messages should strike out the ID if closed
Reported by: | Adrian Holovaty <holovaty at gmail> | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | unscheduled |
Component: | timeline | Version: | 0.8 |
Severity: | minor | Keywords: | |
Cc: | manuzhai@…, Thijs Triemstra, Ryan J Ollos | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
It would be very useful if all "Ticket"-type messages on the timeline would strike out the ID for closed tickets.
For example, in this message:
"Ticket #987 created by mdc @ manbw.dk"
If Ticket #987 has since been resolved, the timeline "Ticket #987 created" message should strike out the "#987" — even if it's a "created" message.
This would convey more information: That the ticket was created but has since been closed.
Attachments (1)
Change History (16)
comment:1 by , 19 years ago
Milestone: | → 0.10 |
---|---|
Owner: | changed from | to
comment:2 by , 19 years ago
Milestone: | 0.10 → 0.11 |
---|---|
Severity: | trivial → minor |
I couldn't make it work for some reasons. I'll try harder later.
comment:3 by , 18 years ago
Cc: | added |
---|
comment:6 by , 18 years ago
Replying to cboos:
Not for 0.11.
Check out t991.diff - I think that's how the new context stuff is supposed to be accessed. However I think the db hit might be a bit much to do it that way especially when showing a large number of high-ticket days. As a config option the db hit would be a choice of the server admin though.
I'm +1 on this feature's availability and am not sure if the punting to 0.12 was just because there's no patch or if there's some discussion I'm missing.
comment:7 by , 18 years ago
The use of the API is correct, but the db hit would be a bit too much, check the Timeline -> much slower thread.
I've looked at the code again, and it seems quite possible to get the current status (current_status is probably a better name than master_status) from the query line 219.
Like most tickets that will get shifted to 0.12, the purpose here was more to clean-up the field and to better reflect what could realistically go into the 0.11 release than to prevent something to be implemented for 0.11 ;-)
comment:8 by , 14 years ago
Milestone: | next-major-0.1X → unscheduled |
---|
comment:9 by , 14 years ago
Cc: | added |
---|
comment:10 by , 11 years ago
I'm using Trac 1.0.1 and this is still a problem. I see that someone unscheduled this task 3 years ago. Could we consider putting it back into the queue and having it implemented?
comment:11 by , 11 years ago
Anyone might dislike use of closedticket
class in timeline.css, we could be the following….?
-
trac/htdocs/css/timeline.css
diff --git a/trac/htdocs/css/timeline.css b/trac/htdocs/css/timeline.css index 8f54614..069e42a 100644
a b dt em { 41 41 font-style: normal; 42 42 text-decoration: none; 43 43 } 44 dt.closedticket em { text-decoration: line-through } 44 45 dt .time { color: #999; font-size: 80%; } 45 46 dt .author { color: #666; } 46 47 dt.highlight { background-color: #ffa; }
comment:12 by , 11 years ago
comment:13 by , 11 years ago
Cc: | added |
---|
comment:14 by , 9 years ago
Owner: | removed |
---|
#2637 requested again the same thing.
Adding this on my virtual TODO list…