Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-12319

jira.field.resolution.exclude - Exclude all the resolutions except one

    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Hi,

      we are creating an workflow and we need to create this property to exclude all of the resolutions except the one we want. Image if I create one more resolution, it will appears on the resolution combo. Is there a way we could exclude all except one, like this:

      jira.field.resolution.exclude

      value: 1,2,3,5,6,*

      PS: this will exclude all the resolutions except the number 4.

      Kind Regards...

      Renato Isidio

            [JRASERVER-12319] jira.field.resolution.exclude - Exclude all the resolutions except one

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Josh Devenny and Roy Krishna JIRA Product Management

            Jose M. added a comment -

            I my opinion, the solution for this issue is to use the "property jira.field.resolution.include", but I am not sure, if the property already exist, see comment: here.

            Regards, José

            Jose M. added a comment - I my opinion, the solution for this issue is to use the "property jira.field.resolution.include", but I am not sure, if the property already exist, see comment: here . Regards, José

              Unassigned Unassigned
              1dfc46856601 Renato Isidio
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: