Best Practices to track the Status? Status or Resolution to avoid redundancy

gowri goli

I am looking for suggestion on the best practices to track the user stories in a Scrum framework. 

We have few detailed statuses like open, design, development, documentation, training and various type of tests before marking the story as complete/done.

We are of the view that we do not need to have Resolution field on the UI as it is not required and status is enough to track the story.

What is the best practice? Can you all share your ideas and what you have ended up doing in your environment?

 

 

Nic Brough -Adaptavist-

Best practice is to go with the software as it is intended to be used.

You need to fill the resolution field appropriately as a good swathe of Jira needs it for reporting and statistics, irrespective of what you do in Scrum.  "Do not need the resolution field" is wrong when talking about Jira, you need it, whether your users use it or not.

You must set up your workflows to handle it correctly.  The simplified workflow includes a "set resolution" flag on columns - use it.  If you're using the workflows generated automatically by project create templates, it will handle it ok for you.  If you are editing your own workflows, then

• Always clear the resolution with a post-function when "reopening" it (usually, a transition from a green status to a non-green one).  Use "update issue field", resolution -> none
• On transitions from open to closed (usually non-green status to a green one), either have
  • Resolution on the transition screen
  • A post-function that set the resolution
• Never put the resolution on any other screen

This is not an optional field, if you want your Jira to work properly.  You have to do these things.  (There's an essay on how I could or would replace it with a better system, but we're stuck with this at the moment)