Resolution is a rather annoying field. To my knowledge you cannot have different values on different projects and it's not very useful for us.
So I'm thinking about hiding it in all our field configurations.
I expect the "assigned to me" gadget as well as all the filters using resolution to not work anymore, but is that all?
Is there anyone who did something similar?
A better approach is to set the resolution in the workflows silently, so the user never gets involved. Then everything else will continue to work (and if you want to completely force it, you can remove all the resolutions you don't want to use at all)
However, there are options for limiting the list of resolutions too. Not at a project level, but at workflow - see https://confluence.atlassian.com/jira/workflow-properties-189949.html
Thank you @Nic Brough [Adaptavist], @Taha and Joe Pitt.
We already set resolution with post-functions most of the time, but we haven't got a clear policy on that yet, and we have some old projects without this. We are definitely working on this.
However, resolution still shows up on the issue screen and when you export it.
At that point I would still rather give up on the green tick mark on subtasks to not see resolution on screen.
Will I regret it? Is it easier to keep telling people "Don't look at this."
You're giving up a lot of functionality if you don't use resolution. Everything in JIRA looks at it to see "is this done with". Built in project summaries and reports, gadgets with "exclude resolved issues", the strikeout function, marking subtasks complete, and there's a LOT of addons (including Agile and Service Desk) that absolutely rely on it.
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