I don't allow deleting issues and have a Deleted and Cancelled resolutions for those issues that would be deleted. If you use JIRA for change control you would want something for those issues. I suggest using the workflow property to include just those resolutions you want the user to select from. Using the include function avoids needing to update the workflow if you add more resolutions.
https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html
I'd recommend using any resolutions that describe why you have closed an issue. They're there to fit your purposes, and the language you use. The default ones, fixed, won't fix, etc are not a bad starting point (I usually add "duplicate" quite quickly though), but the real answer should be driven by your reporting needs. How do you want to report on "why did we close issues"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Really depends on what you use JIRA for.
If standard SDLC (Software Development Lifecycle) I think the already built ins are enough.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks,
I think these resolutions are enough in SDLC: "Fixed", "Unfixed", "Cancelled" , "Rejected", "Won't Do", and "Duplicate".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.