Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,297,661
Community Members
 
Community Events
165
Community Groups

Status and Automation Rules

We created new statuses as the category assignment was different.  We changed the name slightly.  However the original statuses are part of automation rules that trigger tickets in another board to update their statuses in the tickets.  

How do we get the new statuses to trigger the transition in the other board, if the name does not match?
Are there any potential risks with changing the status names?
Please let me know if there are any workarounds to the above scenario.  Thank you.

1 answer

0 votes
John M Funk Community Leader Jun 10, 2022

Hi Stacey - Welcome to the Atlassian Community!

Changing the name of a Status changes the name in your entire instance and every workflow. Therefore, it is not a good idea to change Status names that are used in multiple places. 

Having said that, you will need to go into each automation and change them manually. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,770 views 37 47
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you