Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-17717

Need a "Issue Type Resolution Scheme".

    XMLWordPrintable

    Details

    • Feedback Policy:
      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.

      Description

      We use JIRA enterprise and need to use a different set of "Resolutions" for each issue type (to avoid showing the use a long list of resolutions where some are not applicable for the current issue type).

      The only way to avoid this seems to be to create a separate workflow for each issue type and then use the "jira.field.resolution.exclude" propery for the "Resolve Issue" transistion to limit which resolutions are presented to the user.

      This solution (the only solutionI know of) requires that a separate workflow be created for each issue type. We really want to use the same workflow for each issue type. But we do want to specify a custom set of resolutions for each issue type. When we do need to change the workflow (i.e., add or modify steps or transistion), we are forced to make the same changes to each workflow for each issue type.

      This could be avoided if Atlassian introduced the concept of an "Issue Type Resolution Scheme". This would be a scheme where each issue type could be mapped to a set of resolutions. With this feature, we could use a single workflow for each issue type and we could have a custom set of resolutions for each issue type.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jeffjira Jeffrey Zelt
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: