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

      Atlassian status as of 24 August 2021

      Hello all,

      Thank you for watching, voting, and commenting on this issue.

      Today, we've rolled out the ability for you to set different workflows per issue type (epics, stories, bugs, tasks, etc.).

      Please don't hesitate to give us your feedback!

      Thank you,

      Bryan Lim
      Product Manager

       

      Problem Definition

      Customer not able to edit workflows in next-gen projects.

      Suggested Solution

      Ability to edit workflows in next-gen projects.

      Why this is important

      Customers willing to migrate from a classic project to a next-gen project want to edit the native workflow to match with the workflow status' of the projects

            [JRACLOUD-85717] Ability to edit workflow in team-managed projects

            We have a next-gen project version of JIRA. I see that there is no per project workflow setting whereas there is one per issue type. That is fine but I have a certain workflow defined which I am not able to copy it to the workflow each issue type. It seems like I have to redraw the whole workflow for each project's issue type. Can you help here?

            Chethan Seshadri added a comment - We have a next-gen project version of JIRA. I see that there is no per project workflow setting whereas there is one per issue type. That is fine but I have a certain workflow defined which I am not able to copy it to the workflow each issue type. It seems like I have to redraw the whole workflow for each project's issue type. Can you help here?

            We are also trying to do this. We have created the new Workflow. We have also created a new Workflow Scheme, and Associated the Issue Type we want to use with this Workflow Scheme. Despite this, the new Workflow Scheme is in the "Inactive" section (despite it being associated with an Issue Type). If we instead check under Project Settings -> Issue Types, this new Workflow is NOT associated with the Issue Type in that table we can see, again despite us having associated the Workflow Scheme with this Issue Type.

            Why is it not possible to associate the correct Workflow from Projects -> PROJECT NAME -> Project settings -> Issue types? This is where you see an overview of Workflow, Field Configuration and Screen for each of your Issue Types, so this would be a great place to be able to edit and change these associations.

            Fredrik Bernsel added a comment - We are also trying to do this. We have created the new Workflow. We have also created a new Workflow Scheme, and Associated the Issue Type we want to use with this Workflow Scheme. Despite this, the new Workflow Scheme is in the "Inactive" section (despite it being associated with an Issue Type). If we instead check under Project Settings -> Issue Types, this new Workflow is NOT associated with the Issue Type in that table we can see, again despite us having associated the Workflow Scheme with this Issue Type. Why is it not possible to associate the correct Workflow from Projects -> PROJECT NAME -> Project settings -> Issue types? This is where you see an overview of Workflow, Field Configuration and Screen for each of your Issue Types, so this would be a great place to be able to edit and change these associations.

            maximilian.koenig added a comment - - edited

            So does this mean that, for example, creating a workflow to be used with a multitude of projects is not possible with next gen projects? This would be rather frustrating because we need to set the same workflow on multiple projects that will then be shown in the same kanban board together.

             

            Also it seems like when adding the newly created workflow states to a multi project board as another lane all the states of the different projects are perceived as their own thing, so I have to add the same state with the same name to the column for each project again. Is there now way to merge workflow states with same names?

            maximilian.koenig added a comment - - edited So does this mean that, for example, creating a workflow to be used with a multitude of projects is not possible with next gen projects? This would be rather frustrating because we need to set the same workflow on multiple projects that will then be shown in the same kanban board together.   Also it seems like when adding the newly created workflow states to a multi project board as another lane all the states of the different projects are perceived as their own thing, so I have to add the same state with the same name to the column for each project again. Is there now way to merge workflow states with same names?

            Hi 0105401005a0 thanks for sharing your feedback. We understand that this new way of saving a different workflow may be a little "scary". In the next 1-2 quarters, we're hoping to introduce some improvements to the saving experience to give users a little more context and hopefully make it more intuitive. Would love to keep in touch and gather your feedback as we work on improving the UX.

            blim (Inactive) added a comment - Hi 0105401005a0  thanks for sharing your feedback. We understand that this new way of saving a different workflow may be a little "scary". In the next 1-2 quarters, we're hoping to introduce some improvements to the saving experience to give users a little more context and hopefully make it more intuitive. Would love to keep in touch and gather your feedback as we work on improving the UX.

            Jeff Petriello added a comment - - edited

            I'm also not seeing this feature. I've created a workflow, added it to a workflow schema (including assigning it to the correct issue type), but see nowhere where I can activate this schema in association with my Project.

             

            If I go to the issue type I'm trying to have a separate workflow for, and click "edit workflow" i see no place to assign it a new one.

             

            EDIT: I have resolved this issue. The next-gen project worfklows aren't created or managed under worfklows at all. You need to create a new one directly from the "Edit Workflow" button that is next to the Issue type under your project settings. It's very scary, but you need to completely manipulate your existing workflow into the new one you want, and then when you hit "Update Workflow" only select the issue type you want that change to apply to. This is NOT very intuitive, as you need to edit a workflow you don't want to change in order to create a new one.

             

            Jeff Petriello added a comment - - edited I'm also not seeing this feature. I've created a workflow, added it to a workflow schema (including assigning it to the correct issue type), but see nowhere where I can activate this schema in association with my Project.   If I go to the issue type I'm trying to have a separate workflow for, and click "edit workflow" i see no place to assign it a new one.   EDIT: I have resolved this issue. The next-gen project worfklows aren't created or managed under worfklows at all. You need to create a new one directly from the "Edit Workflow" button that is next to the Issue type under your project settings. It's very scary, but you need to completely manipulate your existing workflow into the new one you want, and then when you hit "Update Workflow" only select the issue type you want that change to apply to. This is NOT very intuitive, as you need to edit a workflow you don't want to change in order to create a new one.  

            @blim Perfect!  It's exactly what I was looking for.  Thank you for your explanation!  

            Tom Rhineberger added a comment - @blim Perfect!  It's exactly what I was looking for.  Thank you for your explanation!  

            2a91ce736794 Can you email your Jira instance name (by copying from your URL bar) to me at bryan.lim@atlassian.com? Happy to also help troubleshoot via Zoom call

            blim (Inactive) added a comment - 2a91ce736794 Can you email your Jira instance name (by copying from your URL bar) to me at bryan.lim@atlassian.com? Happy to also help troubleshoot via Zoom call

            30b927547d99 When you first go to save a different workflow, you'll need to "split" the workflow from the others after you add your desired statuses and/or transitions. Let me know if that works! See screenshot: 

            blim (Inactive) added a comment - 30b927547d99  When you first go to save a different workflow, you'll need to "split" the workflow from the others after you add your desired statuses and/or transitions. Let me know if that works! See screenshot: 

            When I select Edit workflow for my team-managed project for a Subtask item (or any item type to include Epic), it still shows all issue types in the workflow edit screen.

            Is there something we need to do to get this change to take effect?

            Tom Rhineberger added a comment - When I select  Edit workflow for my team-managed project for a  Subtask item (or any item type to include Epic), it still shows all issue types in the workflow edit screen. Is there something we need to do to get this change to take effect?

            Nilufer Saltuk added a comment - - edited

            This isn't working for my team-managed project, but it is working on my coworker's team-managed project. My Update Workflow button is grayed out. I confirmed that I'm an Admin of the project. The main differences between her project and mine are that mine has automation and Slack and hers doesn't. Do you know why I can't edit?

            Nilufer Saltuk added a comment - - edited This isn't working for my team-managed project, but it is working on my coworker's team-managed project. My Update Workflow button is grayed out. I confirmed that I'm an Admin of the project. The main differences between her project and mine are that mine has automation and Slack and hers doesn't. Do you know why I can't edit?

              blim2@atlassian.com blim (Inactive)
              rdey@atlassian.com Ratnarup
              Votes:
              1495 Vote for this issue
              Watchers:
              759 Start watching this issue

                Created:
                Updated:
                Resolved: