The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Setting an issue value based on a {{lookupIssue}}'s value

Nathan Given
Contributor
February 2, 2022

I'm trying to take a value from a free form text field (single line) and populate a drop down field based on what the user typed in.

However, there are 100+ different options, so I was trying to use the power of Jira and automation rules to make this maintanable for non-programmers.

I thought I could build an automation rule that uses "Lookup issues" to find an issue, then copy the field value from the looked-up issue to the current issue.

Here is my automation rule: 

 

Everything works except the last action to edit the current "Customer" field.

Any ideas what I'm doing wrong?

 

Thank you~!

 

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

6 votes
Answer accepted
Nathan Given
Contributor
February 2, 2022

I figured it out. The lookupIssues project had a different context set for the "Customer" field with different values, so the automation rule couldn't set the triggering issue's "Customer" field to a value that wasn't available in the "Customer" drop down.

 

All fixed!

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events