Defining Resolution Field Values

Resolutions are the ways in which an issue can be closed. JIRA ships with a set of default resolutions, but you can add your own as follows.

Defining a new resolution

Don't create a Resolution named "Unresolved"/"None"

Any issue that has the Resolution field set is treated by JIRA as "resolved". The Issue Navigator displays Unresolved when no resolution is set for an issue. So adding a resolution named Unresolved/None and setting it in an issue will mean that the issue is seen by JIRA as resolved. This will lead to confusion and is not recommended. 

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > Issues. Select Resolutions to open the View Resolutions page, which lists the standard resolutions, along with a form for adding new resolutions.
    (tick) Keyboard shortcut: g + g + start typing resolutions
  3. Complete the Add New Resolution form at the bottom of the page:
    • Name — enter a short phrase that best describes your new resolution.
    • Description — enter a sentence or two to describe when this resolution should be used.

(info) The View Resolutions page can be used to edit, delete, set as default, and re-order the resolutions as they are displayed to the user who is resolving an issue.

Was this helpful?

Thanks for your feedback!

27 Archived comments

  1. User avatar

    timofeyl

    Hello. I need to create some new resolutions for specified project.

    How can I separate/hide part of resolution some projects?

    29 Mar 2011
      1. User avatar

        Anonymous

        is this solution works in JIRA 4?

        30 Mar 2011
        1. User avatar

          timofeyl

          Yes. It works but I have some projects and 15 workflows.

          It is inconveniently to change all workflows.

          07 Jul 2011
      1. User avatar

        Tickstar

        The link is dead. Is this possible in Jira Ondemand as well? Please point me to the guide in that case. I want to create project specific resolutions.

        12 Apr 2012
        1. User avatar

          Karie Kelly

          You can do this on ondemand.  You have to set a property on that workflow transition that moves it to Resolved state and you want them to select the Resolution. See:

          Workflow Properties

          You either include the ones that you want or exclude those ones that you don't want.

          You have to get the internal ID associated with the resolutions that you want to include or exclude. Unfortunately, they are not displayed in the UI when viewing the set of resolutions. You will need to click on Edit associated with the specific resolution and the ID is the last number in the URL.

          To modify your transitions, you will have to create a draft of the workflow, update the transition properties, and republish. 

           

          15 May 2012
          1. User avatar

            Anonymous

            This helped me immensely.  Thanks.

            14 Aug 2012
  2. User avatar

    Veselka Petrova

    Hello. I created new resolutions for my project. One of them is "Complete". Is it possible when I choose this resolution for a task, to change automatically  the Completion from 0% to 100%?

    04 Apr 2011
  3. User avatar

    Anonymous

    Hi, i cannot find Administrations -> Issues -> Resolutions.

    Where do you all find it ?

    I still cannot add options within my resolution.

    Thanks,

    Afraz

    26 Aug 2011
  4. User avatar

    Tickstar

    The path in current Jira OnDemand is Administration > Issues > Issue Attributes Resolutions

    11 Apr 2012
  5. User avatar

    Anonymous

    I need to customize the resolution field. I dont want to see certain options. How do I go about doing this?

    19 Apr 2012
  6. User avatar

    Anonymous

    I created a new resolution and designated it as the default resolution. But, now when users create a new issue it's now crossing out the key as if the issue is resolved. Is there any way to designate the resolution as being open/closed etc? i have no idea what i did or how to fix it.

    02 May 2012
    1. User avatar

      Lisa Rahder

      The Resolution field is very annoying:  any value in that field will cause the story/issue number to be struck-out.

      26 Jul 2013
      1. User avatar

        Matt Doar [ServiceRocket]

        That is how that field works. Chapter 1 of Practical JIRA Administration recommends not adding a resolution such as Unresolved.

        26 Jul 2013
  7. User avatar

    Anonymous

    Hello, is it possible to add more criteria on who is tagged as UNRESOLVED? I have custom resolutions, and some of them are not applicable to be tagged as RESOLVED, for example, CANNOT REPRODUCE, or DUPLICATE. I want those resolutions to be considered also as UNRESOLVED, because in the roadmap page, once you set the resolution to a value, it will be now tagged as resolved, even though it should not be.

     

    Please advise.

    04 Oct 2012
  8. User avatar

    azfa

    how can i add new issue attribute to JIRA issues? what is the way to add the attribute

    15 Oct 2012
  9. User avatar

    Karie Kelly

    You use the Custom Field functionality and add the fields to the screens associated with your specific JIRA issue types.

    15 Oct 2012
  10. User avatar

    Anonymous

    As other users reported before, we also have the same problem.

    We created a new Resolution option and marked it as the default resolution. This Resolution field is set in the Default screen in order to make it editable (otherwise, this field is not editable in the issue screen..., maybe another bug?). And now, when users create a new issue it's now crossing out the key as if the issue is resolved, but it's not!!! Any way to fix it?

    Thanks in advance!

    20 Nov 2012
  11. User avatar

    Anonymous

    I need to set the value of Resolution dynamically. There are ids available for custom fields, likewise is there id available for "Resolution" ?

     

    30 Nov 2012
  12. User avatar

    Anonymous

    It doesn't make sense to set the resolution field while creating an issue because that would mean that it is not an issue anymore as it is resolved . So this field really shouldn't be configured to go at Default Screen but only to be available at Resolve Issue Screen.

    29 Jan 2013
  13. User avatar

    randy zhu

    What would really be nice is the ability to set resolution per issue type.  That would allow extreme flexibility and due away with the silly .include/.exclude functions. 

    28 Feb 2013
  14. User avatar

    varduhi julhakyan

    Is there a possibility to unset the resolution? In my workflow after setting a resolution QA need to verify, in case if there tests failed, they need to reopen the issue that is unset the resolution.

    01 Oct 2013
    1. User avatar

      Karie Kelly

      You can.  We actually have two possible transitions when in QA's queue - Pass and Fail.  On Fail, we have a post function for that transition that clears the resolution field which sets it back to Unresolved.

      01 Oct 2013
  15. User avatar

    Anonymous

    This may already have been answered, but when I create an issue the Resolution is automatically being set to "Fixed". This is a complete pain because I can't get a good count on issue statistics because the system things brand new tickets are resolved.

    05 Mar 2014
  16. User avatar

    Bruce Van Horn

    To me, this seems pretty unforgiving.  The default configuration is set up such that anything you set in that box marks it "resolved" even if you set it to "incomplete", and there is no way to set it back to "Unresolved" so if a developer accidentally sets this field, there is no way to fix it, at least none that I find obvious from the UI.  Personally I would rather have issue numbers with a strikethrough when they are closed.  The notion of a separate / competing resolution field seems odd.  To me the status field should tell you that it is resolved and the resolution field should tell you how it was resolved.  As it is now the resolution field competes with the status and causes confusion by striking out issues that aren't really "done".

    11 Aug 2014
  17. User avatar

    Phu Ngo

    I'm running into the same problem. A developer accidentally changes this and there is no way to get back to "Unresolved".  The only way is to change is via a database change.  I would request Atlassian change the behavior of this field entirely.  

    25 Aug 2014
    1. User avatar

      Chris Cogdon

      Hitting "Reopen Issue" button seems to have done the trick. This is for a standard "Defect" issue type, so it might not be available for what you have.

      21 Jul 2015
Powered by Confluence and Scroll Viewport