Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-8720

Cannot simplify workflow when all issue types are mapped to the same workflow but individually

XMLWordPrintable

      When creating a workflow scheme, if you select the workflows to each issue type one by one, even if you choose the same workflow for all issue types, Greenhopper doesn't allow you to Simplify the Workflow, even if all the other restrictions on Using GreenHopper Simplified Workflow - why Not are true.

      I've attached two screenshots as an example.

      Workaround

      Only map the "All Unassigned issue types" in the workflow scheme.

        1. OnDemand.png
          OnDemand.png
          60 kB
        2. screenshot-1.jpg
          screenshot-1.jpg
          121 kB
        3. Standalone.png
          Standalone.png
          38 kB

          Form Name

            [JSWSERVER-8720] Cannot simplify workflow when all issue types are mapped to the same workflow but individually

            Deleted Account (Inactive) added a comment -

            This problem is still occurring.

            Deleted Account (Inactive) added a comment - This problem is still occurring.

            Peter Reiser added a comment -

            This problem still occures in the lastet Cloud Jira Version

            When will this be fixed ?

            Peter Reiser added a comment - This problem still occures in the lastet Cloud Jira Version When will this be fixed ?

            Peter added a comment -

            This problem still occures in Jira version 7.9.0

            Peter added a comment - This problem still occures in Jira version 7.9.0

            Chad Wilhelm added a comment -

            Hello Tom,

            Did you get a resolution to this?

            Thanks,
            Chad

            Chad Wilhelm added a comment - Hello Tom, Did you get a resolution to this? Thanks, Chad

            Veracode added a comment -

            We are seeing this problem today.

            Problem was that the project had been re-named. Fixed the filter and all is OK.

            Veracode added a comment - We are seeing this problem today. Problem was that the project had been re-named. Fixed the filter and all is OK.

            André van der Zijden added a comment -

            Seeing this is just a minor bug (on which I agree). It would be nice if confluence was updated to also show this information that you have to individual issue type assignments removed.

            I mean this page: https://confluence.atlassian.com/display/AGILE/Using+JIRA+Agile+Simplified+Workflow?src=search#UsingJIRAAgileSimplifiedWorkflow-whyNot

            André van der Zijden added a comment - Seeing this is just a minor bug (on which I agree). It would be nice if confluence was updated to also show this information that you have to individual issue type assignments removed. I mean this page: https://confluence.atlassian.com/display/AGILE/Using+JIRA+Agile+Simplified+Workflow?src=search#UsingJIRAAgileSimplifiedWorkflow-whyNot

            Tom Jackson added a comment -

            I'm seeing this problem with Jira Agile 6.3.1 for a project that maps the "All Unassigned issue types" to a single workflow in the workflow scheme. The project and board satisfies all of the criteria for using the simplified workflow:

            • There is only one project being viewed by the board
            • That project uses a JIRA workflow scheme which only has one workflow for all issue types; and
            • Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian
              • See screenshot-1.jpg attached. Using the default workflow
            • You have the 'JIRA Administrators' global permission; and
            • You are using JIRA version 5.0.4 or later (please see Supported Platforms).
              • Using Jira 6.0.8 with Greenhopper 6.3.1

            Tom Jackson added a comment - I'm seeing this problem with Jira Agile 6.3.1 for a project that maps the "All Unassigned issue types" to a single workflow in the workflow scheme. The project and board satisfies all of the criteria for using the simplified workflow: There is only one project being viewed by the board That project uses a JIRA workflow scheme which only has one workflow for all issue types; and Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian See screenshot-1.jpg attached. Using the default workflow You have the 'JIRA Administrators' global permission; and You are using JIRA version 5.0.4 or later (please see Supported Platforms). Using Jira 6.0.8 with Greenhopper 6.3.1

              Unassigned Unassigned
              cgauterio Clarissa Gauterio (Inactive)
              Affected customers:
              24 This affects my team
              Watchers:
              29 Start watching this issue

                Created:
                Updated: