Need help copying the value of one custom field to another using scriptrunner or automation for JIRA

Louis Andrews February 28, 2022

Hello I am trying to copy the selected users from custom field user picker "New assignee" and "Default Assignee" from one issue to another. I already created issues with the correct assignees already selected. I would like the user to create an issue, select category they want (issue picker), and have their assignees prepopulated.  

I am using a custom field that is an issue picker on a create screen which allows you to select the desired issue without linking. The automation I have sets a custom field to value"{{issue.customfield_11102.key}}" which creates a hyperlink to the selected issue. (This is wanted)

I want to get the custom field user's form "My assignee" and "Default Assignee" (which were previously set) from the issue selected and assign it to the new issue being created.

So far from automation I have only been able to retrieve the key {{issue.customfield_11102.key}} and the summary {{issue.customfield_11102.fields.summary}} of the selected issue. I've tried using the custom fields of New Assignee - customfield_11087 and Default Assignee - customfield_11092 but with no luck. 

Is there a way to get the custom fields I want through automation or should I use scriptrunner? If I were to use scriptrunner are there any references I could use (have yet to find any)?

Please feel free to ask for more information if needed, I understand this may be complex, but this is greatly needed to help prepopulate the users instead of allowing my developers to have to do it every time they create a specific issue type.

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 28, 2022

Hi @Louis Andrews 

As you are noticing for your {{issue.customfield_11102}} information, not all of the other fields are present.  If they were, Jira would potentially need to load every single possible issue in a tree of issues when the rule executes.

Your alternative is to use a branch or Lookup Issues with JQL to get at that issue's complete fields.  Lookup Issues is probably going to be a better approach from what you have described.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events