Group workflow rules to further restrict transitions

[Sharon]

Group workflow rules to further restrict transitions

I'm trying to set-up rules for the following.

1x field with drop-down (5 options)

6x fields that correspond to the drop-down options.

example: if x is selected then x corresponding field must be populated. 

I need to create 31 groups (as more than one option can be selected) Jira only allows 10 groups. Is this a restriction at an application level or amin level?

[Akriti Sagar]

Hi Sharon,

That’s a really good use case you’re working on, and I can see why it gets complex quickly with so many combinations.

To your question: the “10 groups” restriction is an application-level limitation in Jira workflow conditions/validators, not just an admin setting. That’s why you’re running into the cap when trying to create 31 groups.

A couple of potential workarounds you might explore:

Scripted Validators (using apps like ScriptRunner) – these let you build conditional logic beyond the built-in limits.

Automation Rules – in some cases, you can trigger an automation that checks the field values and enforces requirements before allowing progression.

Refactoring the workflow logic – instead of grouping every combination, you might be able to simplify by using field required rules or conditional validators that don’t require every group to be explicitly defined.

If you’re on Jira Cloud, I’d also suggest checking the Automation + Workflow Validator combination, as that often provides more flexibility without hitting the group restriction.

Hopefully Atlassian will expand these limits in the future, but in the meantime, apps and automations are usually the best way around it.

[Sharon]

Thanks Akriti, I will look into your suggestions.