Edgewall Software
Modify

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)

t991.diff (1.7 KB ) - added by Tim Hatch 18 years ago.
Quick patch against r4937

Download all attachments as: .zip

Change History (16)

comment:1 by Christian Boos, 19 years ago

Milestone: 0.10
Owner: changed from Jonas Borgström to Christian Boos

#2637 requested again the same thing.

Adding this on my virtual TODO list…

comment:2 by Christian Boos, 18 years ago

Milestone: 0.100.11
Severity: trivialminor

I couldn't make it work for some reasons. I'll try harder later.

comment:3 by anonymous, 18 years ago

Cc: manuzhai@… added

comment:4 by Tim Hatch, 18 years ago

#4402 was marked as a duplicate.

comment:5 by Christian Boos, 18 years ago

Milestone: 0.110.12

Not for 0.11.

by Tim Hatch, 18 years ago

Attachment: t991.diff added

Quick patch against r4937

in reply to:  5 comment:6 by Tim Hatch, 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 Christian Boos, 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 Remy Blank, 14 years ago

Milestone: next-major-0.1Xunscheduled

comment:9 by Thijs Triemstra, 14 years ago

Cc: Thijs Triemstra added

comment:10 by adrya.stembridge@…, 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 Jun Omae, 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 {  
    4141 font-style: normal;
    4242 text-decoration: none;
    4343}
     44dt.closedticket em { text-decoration: line-through }
    4445dt .time { color: #999; font-size: 80%; }
    4546dt .author { color: #666; }
    4647dt.highlight { background-color: #ffa; }

comment:12 by Christian Boos, 11 years ago

That would only strike through a "closed" event, not all the create/edit timeline events for that ticket, if that ticket is currently closed.

There's probably a way to rework t991.diff​ so that the current status is gathered only once for each ticket in the time span (using one separate query?).

comment:13 by Ryan J Ollos, 11 years ago

Cc: Ryan J Ollos added

comment:14 by Ryan J Ollos, 9 years ago

Owner: Christian Boos removed

comment:15 by Ryan J Ollos, 5 years ago

Topic raised on the mailing list.

Modify Ticket

Change Properties
Set your email in Preferences
Action
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.