Won't Fix
Details
Assignee
Karen PowerKaren PowerReporter
Paul SokolovskyyPaul Sokolovskyy(Deactivated)Upstream
NoPriority
Undecided
Details
Details
Assignee
Karen Power
Karen PowerReporter
Paul Sokolovskyy
Paul Sokolovskyy(Deactivated)Upstream
No
Priority
Checklist
Checklist
Checklist
Sentry
Sentry
Sentry
Created December 6, 2024 at 7:15 AM
Updated December 11, 2024 at 6:18 PM
Resolved December 11, 2024 at 6:18 PM
, I have a small request with which I hope you can help. When I look at 's list of subtasks, I see following:
a
I.e., “Resolved” subitems are shown with a ticket number stricken thru, while “Closed” lose it. That’s a cosmetic issue, but it’s quite helpful to have instant snapshot of what’s done and what’s not. I for one used to like Jira’s subtasks exactly for that reason, and here it doesn’t play for us. I guess it will be only more confusing when we have many more dozen subtickets there. So, could you contact someone managing Jira and make sure that “Closed” items are strike-thru too? Alternative, maybe let’s backtrack to using “Resolved” status as the final one for completed subitems.
P.S. Thinking about it, there’s another difference in the picture above - it’s issue type, “Story” vs “Dependency”. I wonder if that may be the culprit. I already suggested to to use only “Story” as it has full status transition matrix, but I’m not sure what to do about existing “Dependencies”. (In either case, the requirement from my side would be that completed tickets are clearly marked as such, strike-thru works well for that, but they still be around and visible, as some contain important information to refer to [again and again]).
Thanks.