It seems that issues are not consistently stroked through when resolved across all JIRA. It shows ok in Agile boards but it doesn't show up stroke through on other areas of the application. How does JIRA identify issues that will be stroked through?
It happens when a resolution is set on the issue. Note that resolution and resolved status are different. Check out
I understand the difference between "Resolved" status and the resolution field. It is set. I have tested this in both JIRA Cloud and Server and in both cases the issue key is not stroke through even though the issue is in a "Resolved" status and the resolution field has been set. Can you verify this in your instance? I'm testing this in JIRA Server 6.2.7 and JIRA Cloud and I'm getting the same results in both.
The original question had already identified the inconsistency of the strikethrough in various areas of the application.
The question was, "How does JIRA identify issues that will be stroked [sic] through?" The answer, as provided by @Norman Abramovitz here, is that the Resolution field gets populated. That is, it starts out blank and is updated manually, via script, or via workflow, which causes the application to show strikethrough in those screens where it does that.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events