Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-79930

Preserve Workflow Scheme ID after editing workflows in the scheme, where the scheme is shared by multiple projects

XMLWordPrintable

    • 2
    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Preserve Workflow Scheme ID after editing workflows in the scheme, where the scheme is shared by multiple projects 

      Steps to Reproduce

      1. Create project using a shared configuration with existing project.

      2. Projects share a Workflow Scheme.

      3. At least one of the projects needs to have issues using a workflow.

      4. Edit the Workflow Scheme by adding a new workflow

      5. Assign the workflow to the scheme for use with existing issue types.

      6. Publish the change. this will change the Scheme ID to a new value.

       

      Expected Results

      The Workflow Scheme ID changes value. 

      Actual Results

      The Workflow Scheme ID stays the same. This is the result when the Workflow Scheme is not shared between projects. 

      Workaround

      Make a copy of the Workflow Scheme to assign to the projects as a temporary placeholder. Once the placeholder scheme is associated with the projects, you can then edit the production Workflow Scheme without it changing the ID. When finished editing, re-assign to the projects. 

            [JRACLOUD-79930] Preserve Workflow Scheme ID after editing workflows in the scheme, where the scheme is shared by multiple projects

            Marcel Caroly added a comment -

            Hey everyone, thanks for your patience on this one. 

            When fixing JRACLOUD-79847 earlier this year, we moved to new approach to publishing draft workflows schemes. This process performs an active update on the workflow scheme using temporary workflows rather than creating a new workflow scheme for each project being updated. This also resulted in the workflow scheme id being preserved in these changes. 

            Marcel Caroly added a comment - Hey everyone, thanks for your patience on this one.  When fixing JRACLOUD-79847 earlier this year, we moved to new approach to publishing draft workflows schemes. This process performs an active update on the workflow scheme using temporary workflows rather than creating a new workflow scheme for each project being updated. This also resulted in the workflow scheme id being preserved in these changes. 

            Joe Snyder added a comment -

            Hi Gabe! I believe the Expected Results and Actual Results here were intended to be the other way around; that is, we expect the workflow scheme id to remain the same after editing its workflows, but this actually results in the workflow scheme id changing (unless it's not associated to any projects).

            Joe Snyder added a comment - Hi Gabe! I believe the Expected Results and Actual Results here were intended to be the other way around; that is, we expect the workflow scheme id to remain the same after editing its workflows, but this actually results in the workflow scheme id changing (unless it's not associated to any projects).

              mcaroly@atlassian.com Marcel Caroly
              35db8db4a53c Gabe Baldwin
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: