I want to use Automation to compare the values ​​of two projects and push the status.

[彥宏_Luke_ 劉]

I have two projects on hand, one is the PLM project and the other is the Project A project.

Now when the name of project A matches the status name of the PLM project, we hope that the PLM project can automatically advance to the status corresponding to the summary name of project A.

But I tried several times and could only push to the next state.
Please tell me where I am not setting it correctly?

[Bill Sheboy]

Hi @彥宏_Luke_ 劉 

There are two things to consider for the scenario and rule you show:

You are trying to access issues in multiple projects, and so the rule scope must be global or multiple-project.  What is the scope of your rule, as a project-scope rule would not be able to access issues in multiple projects?

The rule you show contains multiple branches over linked issues...

• Branches which could be on more than one thing (e.g., linked issues) are run in parallel and asynchronously.  There is no guarantee of when such branches will complete, up until the last step of the rule.
• For the rule you show, this means all of the branches are likely running at the same time, including overlapping each other and colliding

Kind regards,
Bill

[彥宏_Luke_ 劉]

Hi @Bill Sheboy 

It's already set global.

Yes, I later reversed the order so he would stop after transitioning one state.
However, my current problem is that when Project A cannot be pushed to the status, it can automatically push the status of Project PLM.
The automation I expected is the Summary of project A, and the project with the same push status name is PLM.

e.g One of the ticket summary of Project A is contract, to promote Project PLM to the same state named contract.

[Bill Sheboy]

Please post an image showing the audit log details (under Show More) for the rule execution.  That may explain which steps are running and the cause of the problem.

What are the types of these projects: company-managed, team-managed, or one of each type?

Team-managed projects use independent configurations, including status values.  I believe the status id value must be used when those collide in names across different projects.

[彥宏_Luke_ 劉]

It's all company-managed

[Bill Sheboy]

The issue the rule is branching to is PLM-1.  Is that an epic issue type?

If so, the rule logic which later checks fields like {{issue.epic.summary}} cannot work as an Epic cannot have another Epic as a parent.

If this logic should be more generic, due to adding a level to the issue hierarchy, please change those references to use the parent field instead, such as with {{issue.parent.summary}}

[彥宏_Luke_ 劉]

Yes, both projects use Epic

This is the new Automation I created recently, but it still failed, but I think I should be close to the answer.

[Bill Sheboy]

I did not ask if both projects use Epics...Instead I asked "are both issues the rule is trying to access Epic issue type?"  If so, that your original idea not be possible as one Epic cannot have another as a Parent.

At this point, I recommend submitting a ticket to Atlassian Support to learn how they can help with this scenario: https://support.atlassian.com/contact/#/