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; } } }

Automation Question: Check If Delivery is already attached

Robert Lanckton

I built an automation when the status changes, if Status set to 'In Development' AND when Linked Issues not present: Type: is implemented by, then to create a New Issue on our JSM development project.

For some reason, no matter if an issue has a delivery attached or not, it still creates the project. The audit logs says it passes.
To be safe, I also tested Implements and is idea of, and tested an If Then automation considering when it is and isn't present, and all scenarios ignore the implemented by link.

Is there a reason the automation is not recognizing the issue link type?

Screenshot 2023-06-12 at 9.22.26 AM.png

As a note here is the automation audit log reporting Pass on the Related Issue criteria when a delivery ticket (implemented by) is attached:

Screenshot 2023-06-12 at 9.48.08 AM.png

Accepted answers

Curt Holley

Is it because you have restricted the condition to the "Feature Ideas" project?
If the linked issues are in another board, then you need to add them to the scope (i.e. Multi-Projects) in the Rule details session.

All comments

Curt Holley

Robert Lanckton

I assumed that meant any actions taken would apply to the issue, but you might be right. If so, that is.. maddening lol.

I don't have global permissions, and you can't create a delivery ticket to Idea projects, so I won't be able to test to confirm but I'll partner with an admin to see if they can get it working and let you know if you're right!

Omer Meshar_0f60qw

I think Curt is right and that it limits the search of linked issues to the ideas project only.

Robert Lanckton

You are correct @Curt Holley Thank you SO Much! The odd thing that is hard to get my mind around is that with the automation I was able to generate a new issue in a new project, so I didn't think just checking for 'is implemented by' was restricted to the project type, and instead thought that scope restriction was limited to "edits" of other issues. Don't love the incongruity there but so glad you were able to push me in the right direction.

Good to know!