#5653 closed enhancement (fixed)
Strikethrough closed tickets on Custom Query module.
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.2 |
| Component: | ticket system | Version: | 0.10.3.1 |
| Severity: | minor | Keywords: | query strikethrough |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Take for example the following filter on custom query module:
(Show all ticked by owner)
Status new(ticked) assigned(ticked) reopened(ticked) closed(ticked) Group by owner.
It would be nice to have a view where the closed tickets are marked with a strikethrough line. Right now the only way to discern closed tickets is by looking at the status column.
Perhaps being able to add a second sub-grouping (by owner, status) would also solve this ticket, but the strikethrough seems more plausible right now.
(I took some time to check that no other ticket like this exists, but I am not that confident that this feature is not implemented in 0.10.4 or 0.11. Also there is no query component (like the "report system"), so I leave this ticket in "general".)
Attachments (2)
Change History (15)
by , 17 years ago
| Attachment: | strikethrough-0.10.5-patch.diff added |
|---|
comment:1 by , 17 years ago
I uploaded a patch against 0.10.5dev (stable). I can also upload one against trunk, but since I don't have trunk, I won't be able to test it (see that it works).
comment:3 by , 17 years ago
| Component: | general → ticket system |
|---|---|
| Milestone: | → 0.11.1 |
Well, it's quite worthy to be consistent with the display of tickets numbers.
comment:4 by , 17 years ago
| Type: | defect → enhancement |
|---|
This is also related to #6088 that deals with how to display (or just remove) deleted tickets for for changed queries now that we provide a sample plugin that is likely to be used by many. A strikeout of the whole line could also be used for that purpose.
comment:5 by , 17 years ago
| Milestone: | 0.11.1 → 0.11 |
|---|---|
| Owner: | changed from to |
| Severity: | normal → minor |
| Status: | new → assigned |
Got enough annoyed by this to finally do it ;-)
comment:6 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed in [6600] in a simpler way than the proposed patch, but thanks anyway!
comment:8 by , 17 years ago
This would also be nice if it was added to the report as well. We have some reports that show by component and it would be helpful to see strikethrough lines on closed tickets.
follow-up: 12 comment:9 by , 17 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
The strikethrough doesn't work unless you add the status column to the ticket query. Some of our pages we want to not show the status column to preserve space and just rely on the strikethough to tell if a ticket is open or closed.
comment:10 by , 17 years ago
Actually it may be helpful to add a flag to the TicketQuery macro. Some of our managers like to see the strikethrough were others do not want to see it.
comment:11 by , 17 years ago
| Milestone: | 0.11 → 0.11.1 |
|---|
comment:12 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Replying to jason.trahan@…:
The strikethrough doesn't work unless you add the status column to the ticket query.
Well spotted. Fixed in [7472].
Patch against 0.10.5dev