Automation - Transition linked issue from manual automation to new status

TJay.Gerber April 12, 2024

Hello, I already have a manual automation (screenshot below) where it creates a new story in a different project. i.e. This manual automation is in the Automation section of Project ABC, and the screenshot below shows that it'll create a new issue in Project XYZ.

 

I want the newly created issue in Project XYZ to have a status of "Ready" instead of "Open" but unsure how to do that. Any help would be greatly appreciated!

 

What I've tried:

- created Automation in Project XYZ when a new issue is created, transition status to 'Ready'

- created Automation in Project ABC where added a component after the 'then' to also 'then' transition issue to 'ready' status

 

 

Screenshot 2024-04-12 134835.png

2 answers

1 vote
Gikku
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2024

@TJay.Gerber The below sample rule should work to meet your requirements, make sure that the scope of the automation rule is 'Multiple projects' with both ABC and XYZ projects included. You have to go to the 'Global Automation' page to make the change.

Automation.png

TJay.Gerber April 12, 2024

Ah, thanks, Gikku! That was my worry that it'd have to be in 'multiple projects' as the scope. I have to go to our jira admin for them to allow that and then go back to them to make any edits since, once it's in multiple projects, it locks out any edit access.

Is there any other possible solution and automation that could be created in project XYZ separately?

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2024

Hi @TJay.Gerber 

Couldn't you create a separate Automation Rule in Project XYZ to transition it after creation?

You could...

  • Trigger it on issue creation
  • Check for related issues as the condition, i.e linked issues to Project ABC

...and if this isn't sufficient for limiting scope, when you create the issue in XYZ add a parameter the second rule can refer to - eg.

  • If Label = AutoCreated
  • Then Transition Status to Ready
  • And, remove Label = AutoCreated

Ste

Suggest an answer

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

Atlassian Community Events