-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
7
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
It looks like the feature to display an issue key in strikethrough depends on the issue having been resolved.
This improvement request is to
- add a system parameter:
- Show Keys as strike-through: Never, If Resolved (i.e. Resolution not empty) Based on Status
- add a new field to the Status screen (show issues in this status as strikethrough) that is enabled if the system parameter "Based on Status" is selected.
For example, the end result of a development ticket is status "Closed" - even though "Resolved" has a resolution set, it isn't considered done yet until verified by QA. The end result of a support ticket is "Answered". So, in the status maintenance screen, the statuses "Answered" and "Closed" would be flagged to show the issue in strikethrough font.
This enables people who hate the feature entirely the ability to turn it off; it enables people who like the current functionality to leave it as is, and it allows people to control when the issue is displayed as strikethrough based on status.
Original issue description: show strike through for closed, rather than resolved issues. Our users are confusing struckthrough issues as closed, and I was wondering if it would be possible to make this feature work only once an issue has been closed, not resolved. Because resolved means it hasn't been tested yet. From an implementation point of view, obviously this would have to be configurable to support current usage.
- relates to
-
JRASERVER-19882 Strike through behaviour to be explain in the documentation
- Closed
-
JSWSERVER-4688 Misleading strikethrough in RapidBoard
- Closed
-
JRACLOUD-7211 Allow configuration of when issue keys are shown in strike-through font
- Gathering Interest