nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

彥宏(Luke) 劉

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

Accepted answers

John Funk

Hi Luke,

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

Bill Sheboy

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

All comments

John Funk

Hi Luke,

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

Bill Sheboy

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) 劉

Yes , they're all Epic.

John Funk

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.

彥宏(Luke) 劉

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

jira

project

cloud

jira-cloud

automation