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 copy assignee from linked issue to trigger issue?

Dmytro Shaforost

Hi, guys!

Need help in Jira Automation again

I need to create automation rule for next case:

When Issue status change from "A" to "B"

AND Component EQUALS to "SOME"

Then COPY assignee field from Linked Issue WITH Type = Story TO Trigger Issue

Thanks a lot for your help!

Accepted answers

All comments

Bill Sheboy

Hi @Dmytro Shaforost

What have you tried thus far to solve this?

I recommend using a branch or lookup issues to find the linked issue, save the assignee, and then you should be able to update the trigger issue. If you decide to use the lookup, you can directly use the value in the edit.

trigger: issue transition
action: lookup issues on JQL to get a linked issues of that type
condition: the lookup count equals 1
action: edit issue to copy the assignee from the lookup

Kind regards,
Bill

Dmytro Shaforost

Thanks @Bill Sheboy i give up i can't write jql request to get a linked issues of that type... I don't understand how to get list of linked issues with type story from trigger issue

and how to set a condition count = 1

Dmytro Shaforost

@Bill Sheboy can you help with that?

Bill Sheboy

Please try to use the linkedIssues() function:

https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-linkedIssueslinkedIssues--

For example, to find the linked stories for the trigger issue:

issue IN linkedIssues( {{triggerIssue.key}} ) AND issueType = Story

Please also look at the documentation for lookupIssues and lists to learn about size:

unknown

The following procedure worked for me to copy the assignee from a freshly linked issue:

1. Link the issue you want to link with the "Link issue" action
2. Call the "Re-fetch issue data" action
3. Use the "Edit issue" action (assignee) with the smart value {{issue.issuelinks.first.inwardIssue.assignee}}

Probably only step 3 is relevant for your use case. I just wanted to point out how it works if you just linked the issue in the same automation rule.

Remark: Mind the direction of the issue link. If the issue you want to edit has an outgoing connection, you'll have to replace inwardIssue by outwardIssue.

Hope this helps.

Jason M_

Its been 2 years, but this deserves a callout & a thanks for such a highly succinct & informative answer!

Zach Taylor_db7y0q

This helped me as well. Such a great post, THANK YOU!

Welcome!

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

Quick Links

Find more posts tagged with

automation