One of my colleagues notified an interesting thing and this is:
I activate Resolutions attribute on a project and beside the defaults attributes I create two more. One of the attributes is called 'New' and I set it to be default resolution when you create a new Issue.
So problem is: when I create a new 'Bug Issue' and I set the Resolution field to be New(as default), Bugs with the resolution “new” appear with strike trough even if the Bus Issue is 'In Progress'. This problem is in all project where Resolutions are in use.
No, it's not a bug.
You must never have a resolution that means "not resolved" and you must never put the resolution field on a screen other than a "transition" screen.
To fix your JIRA now you've made the mistakes:
Now you can run a report on all the ones you've broken and analyse how to repair your data
JIRA considers an issue as open if it lacks a value in the Resolution field, and as closed if it has a value in it.
The Resolution field is intended to be used to provide information about what finally happened with the issue once there's nothing else to do with it.
Typical Resolution values include: Fixed, Done, Couldn't reproduce, Answered, Out of scope, Not a bug, Won't do, Finished, Deployed to Production... etc.
The Resolution field shouldn't be used to substitute workflow statuses, which suits much better for marking an issue as 'New'.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot