When the Project A issue ticket ends, the Project B status is automatically advanced to the next sta

彥宏_Luke_ 劉 March 11, 2024

I would like to ask the professional automation experts on the forum.

I want to automatically advance Project B to the next state after Project A is completed.

But according to the Automation I set now, he succeeded, but it will not just advance to the next state. He will directly push the status of Project B to the end.

Please tell me where I am, I didn’t find the problem?

PNG 20240311-174906.png

2 answers

2 accepted

0 votes
Answer accepted
Bill Sheboy
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.
March 11, 2024

Hi @彥宏_Luke_ 劉 

Please post an image of the audit log details showing your rule execution.  That will provide context for which steps in the rule processed.

 

What is the scope of your rule: project, multiple-project, or global?  To access / update issues on other projects, the rule cannot have project-scope.

To confirm the scope, please post an image of the rule details, which is the section showing the rule name and settings.

 

Kind regards,
Bill

彥宏_Luke_ 劉 March 11, 2024

image.pngimage.png

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2024

Hi Luke,

What's the relationship between the issues? Are they both Epics? If not, what issue type is the issue in Project B? 

彥宏_Luke_ 劉 March 11, 2024

 

Yes , they're all Epic.

 

image.png

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2024

It appears from your rule that you have multiple branches that keep progressing the status of the issue. Why are you doing that and not just setting the value to a single status? Why so many branches doing so many different Statuses? They are all firing and passing and keep moving the issue. 

Like Bill Sheboy likes this
彥宏_Luke_ 劉 March 11, 2024

So do I just need to set a branch?
Too many branches caused my project B status to be constantly pushed forward. Is there anything that is more correct or can you give me an example?

Bill Sheboy
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.
March 12, 2024

As John notes, the branching may be the cause of what you are observing:

Branches which could be on more than one thing run in parallel and asynchronously; there is no guarantee of when the branch will finish, up until the last step of the rule.

For the rule you show, this means all of the branch could be running at the same time, they do not run one by one, in the order shown in the rule.

Like 彥宏_Luke_ 劉 likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events