How to apply only certain transitions of a SINGLE workflow depending on the project
Asked by Kevin Dickson:

Hi Community,

I have a number of projects that use similar, but "slightly" different workflows.

Is it possible to use a single workflow, and only allow certain transitions to be available, depending on the project it's applied to?

I'm trying to cut down on using multiple workflows.  
Please refer to image for an example of what I mean.

And, thank you in advance ?

![Using one workflow customized per project.png](https://community.atlassian.com/t5/image/serverpage/image-id/339104i0ED54BC70B927B22/image-size/large?v=v2&px=999 "Using one workflow customized per project.png")


Answers:
author: Hans Polder
body: [@Kevin Dickson](/t5/user/viewprofilepage/user-id/5455377) ,

You could do that using Transition Conditions.

But, this will be tricky as I suspect this will not cover any changing project key (you'll need to update the workflow each time a project key is added or changed)

![Screenshot 2024-07-31 125119.png](https://community.atlassian.com/t5/image/serverpage/image-id/339105i43E3574432487D78/image-size/large?v=v2&px=999 "Screenshot 2024-07-31 125119.png")

comments: author: Kevin Dickson
body: Thanks a ton, Hans - I think this may just work!  

We do have a heap of projects that I've inherited, but each with their own workflows.  
When I broke it them down though, i noted that there are very minor differences to each of the flows, just like the example I shared.  
If we have to add a new project, I will just be sure to document this step ..if it works for the current projects.  
Give me a few hours and I'll test it, and lt you know - great help - thanks again!


author: Hans Polder
body: Hi Kevin,

Happy to help!

Generally, if there are only 2 major types of workflows, I would rather advise you to use 2 separate workflows and switch projects between the two options depending on the need.

Keep in mind that when you need to update the workflow to add other projects to the conditions, it might take a while before the changes are applied since it will update all projects.


author: Kevin Dickson
body: Just a quick update on this solution:

It works perfectly ...if you use the old workflow editor.  
It is NOT available in the new workflow editor.

![2024-08-02_13h51_35.png](https://community.atlassian.com/t5/image/serverpage/image-id/339665i20B168A40FDC25AE/image-size/large?v=v2&px=999 "2024-08-02_13h51_35.png")

**So my question is to Atlassian:**

What happens when the old workflow editor is discontinued?  
Will this functionality (to be able to add conditions to transitions) be available in the new workflow editor before the old one is discontinued?

If not there are going to be a lot of grey hairs.


author: Hans Polder
body: Hi [@Kevin Dickson](/t5/user/viewprofilepage/user-id/5455377) ,

I wouldn't worry about it too much. The new workflow editor is still in its baby shoes and has some maturing to do before you could potentially think about killing the trusty old workflow editor.

Conditions based on field values are really common, so I highly doubt that they will discontinue the old one if this is not supported there.


Tags: cloud

jira-cloud