Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Problem with Issue Fields Condition in Automation Rule in Jira DC


I have are rule where the automation will add a user picker name to the summary of the issue when the issue is created or updated and a name has been choosen in the user picker called 'Presenters'- example below

Original issue Summary : 'Centigrade'

Username choosen in custom field user picker 'Presenters' = Jane Doe

Issue updated

New Summary : 'Jane Doe - Centigrade'

What I don't want to happen is everytime the issue is updated is that the user name gets added again and the result is  'Jane Doe - Jane Doe - Centigrade'

So I thought I could control this with an issue fields condition which blocks the name repeat if the name is already present

I am using this smart value {{ issue.customfield_15028.displayName }} to successfully to find the custom field 'Presenter' display name and update the the summary so I know the smart value syntax is correct.

But when I use it as below as a field condition value for 'does not contain' it does not work to block the repeat of the presenter name in the summary

Any help here would be very much appreciated

Thanks Gordon



1 answer

1 accepted

0 votes
Answer accepted
Arkadiusz Inglot
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.
Oct 17, 2023 • edited


Please select proper trigger for your automation and then edit you summary with new 'semi statgic' value.

In that case You can handle both cases (issue create + update) using different trigger:

  • Field value changed
    • Field: Presenters
    • Change type: Any changes
    • Create issue + Edit issue
  • Edit issue:
    • Field: summary
    • Value: {{issue.customfield_15028.displayName}} - Centigrade

Btw, this may be helpful in future cases and playing with strings in automation:


Thanks very much for your input here Arkadiusz - your answer works for me and you have broadened my limited Jira Automation knowledge!



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events