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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

custom field value + summary

When using automation I set it to work when the custom field is changed. Once it is changed the value gets added to the summary as so: {{issue.custom field name}}{{triggerissue.summary}}. Every time I change the value it gets added in front of the summary (custom field value + custom field value + summary), instead of only changing the value of the custom field in the summary.

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.
Sep 02, 2021 • edited

Hi @Edvinas Puslys  -- Welcome to the Atlassian Community!

For automation questions like this, please consider posting an image of your rule and the audit log.  That will provide context for the community to offer ideas.  Thanks!

For what you are noting, you can solve this if you add some type of separator/delimiter between your field and the original summary.  For example a semicolon.  Then you can use a function like substringAfter() to help.

  • trigger: custom field changes
  • action: edit summary to add the new custom field value
{{issue.custom field name}}{{issue.summary.substringAfter(";")}}

You may need to adjust this to handle the special case when there is not semicolon, or always add one to start.

Best regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events