You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?