Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to use Status and Resolution

We have a lot of different workflows in our projects. I am about to clean up in most of them.

I noticed some projects have more than one "green"-status - i.e. a status where resolution field is set to "Done".

Examples from one project are:

- Status = Done  &  Resolution = Done

- Status = Won't Fix  &  Resolution = Done

- Status = Can't Reproduce  &  Resolution = Done

 

I am considering to change all that to:

- Status = Done  & Resolution = Done

- Status = Done  &  Resolution = Won't Fix

- Status = Done  & Resolution = Can't Reproduce

 

The intention would be that all issues that are "Done" will have "status = Done", and then using the resolution field to tell how it is done.

But I am not sure which of the two solutions is the "best" or the "right" way of doing this.

Is there a correct way or a best practice for this?

2 answers

2 accepted

1 vote
Answer accepted
Jack Community Leader Apr 28, 2021

Your proposed approach is , IMO, the correct approach. 

Thank you.

I have tried to find documentation about how best practice is in relation to Status and Resolution. All I have found is technical descriptions about how to use 'resolution' and where to be careful when configuring Jira.

Do you know of any documentation or descriptions about best practices or right use of 'done status' and resolutions?

1 vote
Answer accepted
Joe Pitt Community Leader Apr 29, 2021

I agree with @Jack about your approach. I've never seen a 'best practice' document about that. Jira can be configured in so many ways it would be hard to pin down a best practice other than the resolution field must be set when an issue is 'done' To me, the 'done' status shows no more work is needed and the resolution field indicates the reason the work is done. 

Thank you both of you

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

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

Events near you