Hello i have a question to Resolution field. I do not really understand which is his use. Since i already have statuses like closed and so on. Why do i still need a Resolution field. Could you explain me the use of this Field and what i have to take in concern when using it ?

6 answers

Resolution tells you why an issue was closed. You do only need one CLOSED state (and i recommend this). I think many reports in JIRA use this field.

In addition to the responses above a resolution may be set before the issue is closed to allow for another user to review the issue and confirm prior to closure.

1 votes

In addition to the other answers, be very careful with the field.  A couple of simple points about it:

  1. JIRA, and many of its add-ons use Resolution as the basic "we need to do something with this issue" /  "this issue is done" flag.  If you hide resolution and don't set it at all, then your issues are all going to be open and most of JIRA's functions will tell you that.
  2. Never put resolution on the "edit" screen.  Your users will accidentally set the resolution.

If you don't want to use resolution at all, then teach your administrators to hide it, but build workflows that set it (and clear it) at the right points.

 

As Mike has mentioned above, a resolution lets users know what a particular issues was closed e.g. Fixed

This resolution might be used for a Bug issue type for example.

When a resolution is set on a issue it puts a strikethrough on the resolved issues.

This allows users to visually see what issues are resolved. 

Dear @Corinna as @Mike Friedrich mention is very correct way , but that can used it multiple way.

We are using resolution field for getting issue from different projects.

Suppose 2 projects we are getting with different workflow.
w1 = Pending - Ready for Review - Design - In Progress - Review - Testing - Closed

w2- Open - Design - Implemention  - Manager Review - Closed

So we are consider W1- W2 Starting 2 transition is As Pending  next 2 transition as In Progress and last transition consider as closed.

now we want Status Which is still in pending ..
as writing query and reminding all status with big workflow we are using resolution field as group of some status.
so we can get value easily.

Thank you.

A developer should never just close an issue he thinks he solved. Instead the issue will usually go to the "Resolved" status so QA can verify and close. Resolution tells you WHY the assignee thinks the issue is no longer his or her problem. e.g. "I fixed this" would be resolved with the resolution Fixed. "There is no problem here" would be resolved as Not an issue. "We have another issue that describes the same problem" would be resolved - duplicate. "This is not a good idea" would be resolved - wontfix. Before closing the issue, QA will examine the resolution and know whether to test a fix or not.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

461 views 1 15
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot