The strikeout of resolved issues is common through Jira and Greenhopper. If you want to remove it, then you need to a) change code in several places and b) educate your users that you are removing information that many find useful
I think a better start might be to explain *why* you want to remove this function. I'm sure you have a good reason to think about doing it, but there's probably a far better answer than removing it.
No. Either the resolution is null/empty (unresolved) or it has a value (resolved).
"pending" would not be clear as to whether it is resolved or not, so you should not use it for this. "Not going to do this for a while" is fine, but it is a status, not the reason you are closing something. Move it into the workflow.
...ollected feedback from users around the lack of shortcuts, and we’re here to address that: In next-gen projects, I miss the keyboard shortcuts badly. This is particularly true on the Board, but also i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event