When I read this article on best practices when using the Resolution field, all criteria are met in our workflows.
At the moment of resolving the issue, we do split the resolution into 2 transitions Fix Issue or Abort issue, which respectively sets Resolution to Fix or Abort. This way we can distinguish easily the real problems that were fixed versus the user errors, no business cases etc.
Now among our users is a project lead who wants to get rid of the Resolution field. I tried to convince him with the arguments stated in the article, but he is not convinced.
How do I convince him, and are there among you use cases where the resolution has more than one option?
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