Workflow Condition/Validator based on Project category

[Danilo Simic]

Hello everyone,

I was wondering if there is an efficient way to block a transition based on the project category.

For example if a project is in category A then block the transition. If the project is in category B then allow that same transition to happen.

I am only looking for out of the box solutions for now. I am aware that there are plugins that can solve this but we do not have enough use cases for these plugins to justify the cost.

Thank you

[Maciej Dudziak _Forgappify_]

Hi @Danilo Simic

I don't think it's possible in Jira out of the box, at least not in an easy way. However, with a validator based on Jira expression, it would be simple, as follows:

["Catagory A"].includes(issue.project.projectCategory?.name)

If the project is categorized as "Category A," then allow the transition; otherwise, block it.

I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira free app. You could give it a try. 

Cheers

[Danilo Simic]

Too bad that Atlassian does not have a built in validator/condition that would check a Jira expression.

Thank you for the suggestion, we will be sure to check it out.

[Jeroen Poismans]

Hi Danilo and Welcome to the Atlassian community!

Unfortunately there is no way of doing this natively, but that's probably for a reason. I assume you want to do this so you can keep as few workflows as possible to maintain, which is a good reflex!

However when a project or project category requires that certain transitions should not be available, this might be a use case where creating a new workflow is recommended in order to keep the workflow simple and easier to maintain.

Jeroen

[Danilo Simic]

Hello,

We want to use the same workflow for multiple project because the business needs are almost completely the same. The only difference would be automation rules and the possibility to skip some statues in some cases (which would be specific for a certain project category).

The simplest solution would have been to do this which I asked about.

It is important to add that we have a few dozen automation rules for which the scope is 50+ projects. Splitting the workflows would have worked if we could manually update those rules quickly every time. The quickest solution would have been to add a JQL condition to the automation rule and limit the rule there to a specific project category.

Our use case is a bit specific so we ran into this problem.

Thank you for the suggestion.