Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I configure my Jira project to use a unique workflow scheme for each component defined?

Jason Bernas August 10, 2025

How do I configure my Jira project to use a unique workflow scheme for each component defined?

 

For example component A would use Workflow A.

Component B would use Workflow B.

2 answers

1 vote
Jeroen Poismans
Community Champion
August 10, 2025

Hi and welcome to the community!

Workflows can differ in a different project and for another issuetype. Those are basically the 2 options. 

If you want slightly different approach within a workflow, based on components, you can try to achieve this with conditions (hiding for component A and showing fro component B).

If that is not enough, really consider creating a separate project / issue type for both, because then clearly they require a different process.

Jeroen

Jason Bernas August 11, 2025

Jeroen – Thank you for describing my options. I have not considered taking different workflow transitions based on components.

My use case requires one Jira project. Can you point me to instructions or examples of how to introduce different workflow transitions based on components?

0 votes
ahsanriaz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 11, 2025

In Jira, workflows are attached to issue types, not components. You can still achieve “component-specific” behavior in two ways:

Option 1: Single workflow with branched paths (same issue type)

Build one workflow that contains separate paths for each component (e.g., A-path, B-path).

Add conditions/validators on transitions so only issues with the matching Component can use that path.

(Optional) Use automation on issue create to set the initial status based on Component.

Option 2: Multiple issue types mapped to different workflows

Create separate issue types per component (e.g., “Bug – Component A”, “Bug – Component B”).

Map each issue type to its own workflow in the Workflow Scheme.

Use Automation on issue create to detect the Component and change the issue type accordingly.

Recommendation:
If you want a pure native approach and clear separation, use Option 2. If you prefer to keep a single issue type and don’t mind a more complex workflow (or using apps like ScriptRunner/JMWE for conditions), use Option 1.

Jason Bernas August 11, 2025

Thank you for articulating my options. I intended to follow Option 2. However, in Automation I'm having trouble to Add an action.

My Automation rule is:

When: Value changes for 'Components'

Components contains any of "FW Integration"

Then: Add an action

I don't know how change the issue type on the last step.

ahsanriaz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 11, 2025

Screenshot 2025-08-12 at 9.41.29 AM.png

Jason Bernas August 12, 2025

Screenshot 2025-08-12 at 9.18.31 AM.png

Thank you for your snapshot. It was helpful. I followed it and enabled the automation rule. However, it did not take affect.

My snapshot above indicates it is enabled. 

I don't know how to confirm the automation rule is taking any action or it cannot overwrite these defined workflow schemes.

Screenshot 2025-08-12 at 9.22.47 AM.png

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events