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

How to update the status of specific linked tickets when a primary ticket is transitioned

Sarah Coles

Hello! I've attached screenshots of my jira automation for context. I am trying to have the status of all tickets linked in a specific way updated when a ticket in my product board project is transitioned. I tested this between two tickets and I continue to receive the "no actions performed" response as if the linkage isn't being recognized. Both projects have identical statuses. Please help!

Trigger:

Condition:

Branch:

Branch Action (to be performed on the linked tickets)

Example ticket linkage that didn't result in any action:

Rule details:

Audit log: isn't considering the linked ticket as valid

Screen Shot 2022-05-16 at 4.36.12 PM.png

Accepted answers

Bill Sheboy

Hi @Sarah Coles

I notice a couple of things:

The issue shown in the audit log is not in the PROD project, and so fails the first condition...so no more processed. Is that what you wanted?

Next, I see the "Allow Rule Trigger" option is enabled. That means this rule can lead to triggering itself for other linked issues, potentially looping back on itself...And that will most likely halt execution due to processing time usage. Do you expect a need for this rule to trigger itself?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Sarah Coles

I notice a couple of things:

The issue shown in the audit log is not in the PROD project, and so fails the first condition...so no more processed. Is that what you wanted?

Kind regards,
Bill

Sarah Coles

Hi Bill,

Thanks for your reply! I pulled a poor example error from the audit log - this is now resolved and I also disabled the "Allow Rule Trigger", which seemed to get me closer to solving this as there is no need for the rule to trigger itself

The status transition and linked tasks are now successfully getting recognized, however it is giving me an error related to status translation. Both the PROD and TPB projects have the same statuses, therefore I'm not sure why it is not accepting the copy from Trigger issue command. Is there something else I need to do when defining the status transition to apply to the linked tasks (i.e. using status codes for example?)

I've attached the audit log response below

Screen Shot 2022-05-17 at 10.12.44 AM.png

Bill Sheboy

Are these company-managed or team-managed projects, or one of each?

Company-managed projects use shared definitions of status and team-managed projects each have their own definition of status values...even though the names might be the same (e.g. Backlog and Backlog). So multi-project rules impacting team-managed projects are often more complex to handle this difference.

Sarah Coles

@Bill Sheboy Hi Bill, both projects are company-managed using shared statuses, by mentioning this I did realize one of the projects was missing a status from the other so i updated the workflow scheme and it now works. Thanks so much for your help!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

atl-gruland