Forums

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

Updating Separate Workflows in The Same Project

Luke Burns
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!
September 5, 2025

I have two different workflows enabled for a project for three different work types:

  • Bug
  • Request
  • Build

Bug & request share the same workflow, while build has it's own. My goal is to update the workflow for the build tickets so they can have unique statuses for a different team. Anytime I update one workflow the changes are automatically applied in the other. 

Is this a bug? Do I have an improper config?

Thanks in advance. 

image.png

2 answers

2 accepted

8 votes
Answer accepted
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 5, 2025

Hi @Luke Burns 

Welcome to the community.

You will need to create new statuses in the workflow for work item Build, if you rename a status, this effect any workflow where this status is also used.

Luke Burns
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!
September 7, 2025

Thank you very much Marc. 

2 votes
Answer accepted
Prateek
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!
September 5, 2025

 

What you're experiencing isn't a bug, but rather a nuance of how shared statuses work across workflows in Jira. Here's what's happening:
 Shared Status Behavior When you rename or modify a status (like changing its name or properties), that change applies to all workflows using that status — even if those workflows are assigned to different issue types. This is because statuses are global objects in Jira, not workflow-specific.

What You Can Do To give your Build workflow unique statuses:

  • Create new, distinct statuses (e.g., “Build In Progress” instead of “In Progress”)

  • Assign those new statuses only to the Build workflow

  • Avoid reusing statuses that are already part of the Bug/Request workflow

This way, updates to the Build workflow won’t affect the others.

If you’re working in a team-managed project, the behavior may differ slightly — but for company-managed projects, this is the standard approach.

Let me know if you’d like help mapping out a clean workflow structure or naming conventions for your teams!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events