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 When status changes add comment on linked issue

Colleen Cosgrove_214g2b

I would like to automate adding a comment on a linked issue of a particular type when the issue goes into a given state

I tried the following... not sure how to add fix version in comment but i didn't get the comment anyway - it gets triggered but cannot find the linked ticket - the ticket is linked - see screenshot

Screenshot 2024-07-22 at 6.40.39 PM.png Screenshot 2024-07-22 at 6.42.40 PM.png Screenshot 2024-07-22 at 6.44.19 PM.png

Accepted answers

All comments

Trudy P Claspill

Hello @Colleen Cosgrove

Welcome to the Atlassian community.

Have you tried to create this rule yet? Show us what you have so far, and tell us the part with which you are struggling.

Are the transitioning issue and the linked issue always going to be in the same project, or might they be in different projects?

Colleen Cosgrove_214g2b

they are different projects... i have put what i have so far in the original ticket and the audit of what happens

Trudy P Claspill

Thank you for that additional information, @Colleen Cosgrove

To have a rule triggered by an action in one project and from that cause a change to an issue in a different project, your rule will have to be a Multiple Project Scoped rule.

Such rules can be created only by Jira (Application) Administrators. They can't be created by Project Administrators. Are you a Jira Administrator?

A Jira Administrator would need to navigate to the Global Automation page. This is accessed by clicking the gear icon near your avatar in the upper right corner on the application's menu bar. From there one selects System, which displays the System some of the overarching System wide configuration options, including Global Automation.

On that page the Jira Admin would find the rule you have created, open it for editing, and navigate to the Rule Details page.

From there the admin would change the Scope of the rule to Multiple Projects, and then select the two projects in the Projects list.

Screenshot 2024-07-22 at 4.28.33 PM.png

Screenshot 2024-07-22 at 4.28.45 PM.png

After doing that and saving the change, your rule would then be triggered by an Issue Transitioned event occurring in either project. If you only want the rule to proceed only if the transition occurs for the issue in the BAS project, you would need to add a condition to check the Project field.

If you want the rule to proceed to update linked issues only from the NAS project, then you would want to add a condition within the branch also to check the Project field of the linked issue.

Screenshot 2024-07-22 at 4.35.52 PM.png

Colleen Cosgrove_214g2b

Great!!! thank you so much... how do i reference the fix version from the originating ticket in the comment?

Colleen Cosgrove_214g2b

Thanks for the pointers... I have tried both:

A fix for this ticket has been included in the {{triggerIssue}}
{{#lookupIssues.fixVersion}}
{{/}}
release

and A fix for this ticket has been included in the {{triggerIssue.fixVersion}}
release

but neither worked

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