Best practice for a workflow condition on project rather than permission or role

[Kayleen Cucugliello]

Does anyone have a best practice to add a condition to a workflow that allows a status to be hidden in certain projects instead of creating a branch new workflow?

Or is creating another workflow a better practice?

[John Funk]

Hi Kayleen,

It depends on what you are doing, but I almost always suggest using Conditions and maintaining fewer workflows. 

[Simon König]

Hi,

it might be possible to add a condition that checks a project name/key via string comparison.

I don't think this would be best practice since Workflows are fixed to IssueTypes and those then to Projects. If you use the same IssueType, then you could change the WorkflowScheme in the project and just use a different workflow for this one project.

Of course you are able to do this, but:

If you have multiple projects or want to add some in the future, you will always have to be careful when using this condition. And when you e.g. change the project name, your condition will fail too. It is just not as easy to maintain as using a different workflow. In my opinion.