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 particular linked issue when sprint completes

sacha_rouzkhosh

Hi,

I need your help to understand why, during the execution of my automation, the targeted link is not found. Here is the current automation:

Regardless of the value of the "tests" or "is tested by" link, the link is never found.

Do you know why?

Thanks a lot for your help.

Accepted answers

Trudy P Claspill

Hello @sacha_rouzkhosh

Please show us the output in the Audit Log for execution of the rule.

Can you also show us the details of issues in the sprint that have these links?

Are to linked issues in the same project or different projects? If they are in different projects, the Project Scope of the rule would have to encompass all the related projects where the linked issues could exist.

All comments

Trudy P Claspill

Hello @sacha_rouzkhosh

Please show us the output in the Audit Log for execution of the rule.

Can you also show us the details of issues in the sprint that have these links?

Bill Sheboy

Hi @sacha_rouzkhosh

Would you please post an image of the audit log details showing the rule execution? That may help provide context for what is happening. Thanks!

Kind regards,
Bill

sacha_rouzkhosh

Hi,

Yes you're right.

Please find below more details:

Issue to be updated:

Issue that part of the closing sprint:

Thanks for your help.

sacha_rouzkhosh

Hi @Bill Sheboy

Please see my response to @Trudy P Claspill

Thanks for your help

Trudy P Claspill

Thank you for the additional information, @sacha_rouzkhosh

What are the details of the "Linked issues present" condition?

I see that in TESTNEP-24 you have the link "is tested by" TESTBA-14. Have you tried setting the condition to links of type "is tested by"? Can you try that and then show us the output from the audit log?

sacha_rouzkhosh

Hi,

Well... that's strange, that's exactly what I did. I even left the condition to "all types," but the condition was never met. But now it's working with "is tested by". Maybe Jira uses some sort of cache or something that causes config changes to take time to be applied.

Thanks anyway guys!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

sprint