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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Luke,
What's the relationship between the issues? Are they both Epics? If not, what issue type is the issue in Project B?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.