• 122
    • 6
    • Hide
      Atlassian Update – 16 April  2019

      Hi everyone,

      We've reviewed this suggestion again and it remains a potential addition to our longer-term roadmap. This is not yet part of our plans for the nearest 6-12 months. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      To read about our recent investments, please check out this community post on bringing more visibility into what's coming in Jira Server and Data Center

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 16 April  2019 Hi everyone, We've reviewed this suggestion again and it remains a potential addition to our longer-term roadmap. This is not yet part of our plans for the nearest 6-12 months. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap. To learn more on how your suggestions are reviewed, see our  updated workflow for server feature suggestions . To read about our recent investments, please check out this  community post  on bringing more visibility into what's coming in Jira Server and Data Center Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      This suggestion has been separated from JRASERVER-3821 as a separate feature request which we'll prioritise independently. We will use all the comments around resolutions from the original suggestion (JRASERVER-3821) in the design of the feature, so no need to put the same comments, just make sure to vote and watch the issue! We will provide further updates in here.

      Original Request

      As a JIRA Administrator I need more granular configuration for my projects.

      Depending on the issue type, the resolution may be different. For example: in case of bugs, the resolution may be set to "fixed", but in case of improvements there is nothing to fix and the resolution should rather be "implemented". I need to be able to specify the default resolution separately per each issue type.

          Form Name

            [JRASERVER-65924] Resolutions per issue type

            EKP added a comment -

            I came across this thread as I had been frantically searching for a solution to customize resolution options per workflow, resolve screen or project. Usually, Jira has so many options for customization, and it appears that it's not the case here. What a pity!

            The Resolve field gets pulled into reports within a plugin that runs on Jira and we love the fact that we can create our own resolution options that get displayed on the report. However, as some other users are pointing out here, it's not quite convenient or desired to have ALL resolution options appear, when many aren't applicable for certain projects.

            Please reconsider moving this request up to a higher priority! Thanks!

            EKP added a comment - I came across this thread as I had been frantically searching for a solution to customize resolution options per workflow, resolve screen or project. Usually, Jira has so many options for customization, and it appears that it's not the case here. What a pity! The Resolve field gets pulled into reports within a plugin that runs on Jira and we love the fact that we can create our own resolution options that get displayed on the report. However, as some other users are pointing out here, it's not quite convenient or desired to have ALL resolution options appear, when many aren't applicable for certain projects. Please reconsider moving this request up to a higher priority! Thanks!

            Our Jira instance has been running for 17 years now. The amount of available resolutions has grown to 12, which does not sound that much compared to many other configuration items. But it has become very difficult to receive acceptance by our users in regards of being able to customize "everything" - except resolutions per issuetype or project...

            Thomas Abraham added a comment - Our Jira instance has been running for 17 years now. The amount of available resolutions has grown to 12, which does not sound that much compared to many other configuration items. But it has become very difficult to receive acceptance by our users in regards of being able to customize "everything" - except resolutions per issuetype or project...

            I know it 'works' for us now, but adding this feature would make for a better customer experience, making your existing customers that much more loyal.

            Greg LaViolette added a comment - I know it 'works' for us now, but adding this feature would make for a better customer experience, making your existing customers that much more loyal.

            ccec159dff03, there is JRACLOUD-80093 "Resolution per Issue Type", current status "Under Consideration".

            Kalle Niemitalo added a comment - ccec159dff03 , there is JRACLOUD-80093 "Resolution per Issue Type", current status "Under Consideration".

            Piotr Janik added a comment - - edited

            ccec159dff03 This is JRASERVER, not JRACLOUD. If there's no ticket in JRACLOUD linked to this one (or to JRASERVER-3821, or to JRASERVER-5453), I'm afraid it's not even Gathering Interest for them. (There's CLOUD-6554, linked to JRASERVER-3821, but it seems to be in a legacy project, and it's closed anyway).

            Piotr Janik added a comment - - edited ccec159dff03 This is JRASERVER, not JRACLOUD. If there's no ticket in JRACLOUD linked to this one (or to JRASERVER-3821 , or to JRASERVER-5453 ), I'm afraid it's not even Gathering Interest for them. (There's CLOUD-6554 , linked to JRASERVER-3821 , but it seems to be in a legacy project, and it's closed anyway).

            Rakshith A added a comment -

            Hello,

            can you link it to this issue as well https://jira.atlassian.com/browse/JRASERVER-5453

            users end up going that link, & its closed

            Rakshith A added a comment - Hello, can you link it to this issue as well https://jira.atlassian.com/browse/JRASERVER-5453 users end up going that link, & its closed

            Inna S added a comment -

            Hi, do you have ETA for when it will be available in Jira Software Cloud?

            Inna S added a comment - Hi, do you have ETA for when it will be available in Jira Software Cloud?

            Already working on a workaround to only allow the required issue resolutions per issue type, but this has to be done for all Projects so that the Resolution list does not become swamped 

            David Harkins added a comment - Already working on a workaround to only allow the required issue resolutions per issue type, but this has to be done for all Projects so that the Resolution list does not become swamped 

            Dear Jira gods, this is obviously a much needed feature, please implement it!

            Daniel Valenzuela added a comment - Dear Jira gods, this is obviously a much needed feature, please implement it!

              Unassigned Unassigned
              jlazinski Jakub Lazinski (Inactive)
              Votes:
              712 Vote for this issue
              Watchers:
              380 Start watching this issue

                Created:
                Updated: