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:Ā 

Use legacy automations to edit summary with smart values

Derek
November 22, 2023

I want to make/use legacy automations to edit summary after ticket creation. I know you can do it with automations but not that atlassian is limiting automations I want to utilize Legacy. In new automations you use {{issue.reporter.displayName}} and the previous would be something like $reporter.displayName or for custom fields would be {{issue.customfield_****}} and legacy would be $customfield_Get(****). Any advice would be appreciated!

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Joseph Chung Yin
Community Champion
November 22, 2023

@Derek -

I don't believe you can use smart value against legacy automations.  It is always the best to convert your legacy automation to use the new automation rules for your JSM project.

Sorry.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

0 votes
Marc -Devoteam-
Community Champion
November 23, 2023

Hi @Derek 

Smart values are not available in legacy automation as @Joseph Chung Yin mentioned.

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

Atlassian Community Events