Automatically Update a Custom Field

Taryn Lachter
Contributor
October 30, 2024

I am trying to use automations to update a custom field we have called "Stakeholder" which would assign a user within our company. 

Screenshot 2024-10-30 at 9.58.58 AM.png

I'd like it to be based on the ticket's creator - our system automatically assigns the reporter as the creator if it's an internal ticket - but I have tried both smart values below and neither work:

 

{{creator.displayName}}

{{issue.reporter.displayName}}

 

2 answers

1 accepted

3 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 30, 2024

Hello @Taryn Lachter 

Is Stakeholder a user picker/People field?

If so then you can Copy the value from another user field (i.e. Creator) into it.

 

Click the ... button next to the data entry space for the field, and select COPY.

Screenshot 2024-10-30 at 8.04.49 AM.png

 

Click on the text that display in the entry field.

Screenshot 2024-10-30 at 8.05.18 AM.png

Click on the Field to copy value from and select Creator

 

Screenshot 2024-10-30 at 8.05.43 AM.png

Taryn Lachter
Contributor
October 30, 2024

WOOOO this did it THANK YOU

Like Trudy Claspill likes this
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 30, 2024

Glad I could help.

Please consider clicking on the Accept Answer button to mark your Question as Solved. This helps others searching for answers find the posts with validated solutions.

0 votes
Jim Knepley - ReleaseTEAM
Atlassian Partner
October 30, 2024

Hi @Taryn Lachter 

What is the type of the Stakeholder custom field? If it's a "user" type, you'll want to use the {{creator.accountId}} smart value.

The "user" type represents "users identified by Atlassian account IDs." I think that choice was made because of GDPR considerations.

ref: https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events