Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,299,230
Community Members
 
Community Events
165
Community Groups

How to refer to trigger issue field in linked issues while doing automation

Hi,

 

I am automating scenario where I have put trigger condition as change of field "Sprint"

if this field is changed, then it will check Linked issue and copy the Sprint field from trigger issue to Linked issue. 

I am also generating email to reporter with reference of Sprint version. Now I am not able to understand how do I refer to Sprint version of trigger issue. I am using {{Issue.sprint}} but that doesnt return the right value as this rule is under Linked script. 

 

Would it be something like {{issue.triggersprint}}? 

1 answer

1 accepted

1 vote
Answer accepted

Hi @Peyush Agarwal 

You should use a Branch in the automation rule and set this to action all of the linked issues.

Then using an Edit Issues action under this branch, selecting the Sprint field from the dropwdown, you can click on the 3 dots and select Copy from, and select the Trigger Issue as seen below.

You can then either add the email action directly under the Edit Issues action (which will send the email to reporter of all of the linked issues) or you can add the email action outside of the branch, which will only send the one email to the reporter of the triggering task.

Hope this helps, let me know if you have any questions!

auto rule.png

Also if you need to use any smart values in the email, check out this link for all of the sprint-related smart values available - I think from what you've described, you're looking for the Sprint Name, which would be {{sprint.name}}.

Thanks a lot this should help me a lot 

How would you go about reversing this logic? Meaning, I want the Sprint field in the linked issue to update the Sprint field in the trigger ticket. I should note that the Trigger and Linked tickets are in two separate projects.

 

Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Coming Soon: Insight Changing to Assets

The 2020 acquisition of Mindville added powerful asset and configuration management capabilities to Jira Service Management in the form of Insight. Following the completion of that integration, custo...

361 views 3 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you