Edgewall Software

Ticket #991 (new defect)

Opened 4 years ago

Last modified 21 months ago

Timeline Ticket messages should strike out the ID if closed

Reported by: Adrian Holovaty <holovaty at gmail> Owned by: cboos
Priority: low Milestone: 0.13
Component: timeline Version: 0.8
Severity: minor Keywords:
Cc: manuzhai@…

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

t991.diff (1.7 KB) - added by thatch 21 months ago.
Quick patch against r4937

Change History

  Changed 3 years ago by cboos

  • owner changed from jonas to cboos
  • milestone set to 0.10

#2637 requested again the same thing.

Adding this on my virtual TODO list...

  Changed 3 years ago by cboos

  • severity changed from trivial to minor
  • milestone changed from 0.10 to 0.11

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

  Changed 2 years ago by anonymous

  • cc manuzhai@… added

  Changed 2 years ago by thatch

#4402 was marked as a duplicate.

follow-up: ↓ 6   Changed 21 months ago by cboos

  • milestone changed from 0.11 to 0.12

Not for 0.11.

Changed 21 months ago by thatch

Quick patch against r4937

in reply to: ↑ 5   Changed 21 months ago by thatch

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.

  Changed 21 months ago by cboos

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 ;-)

Add/Change #991 (Timeline Ticket messages should strike out the ID if closed)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from cboos. Next status will be 'new'
The owner will change from cboos to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.