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
4,363,767
Community Members
 
Community Events
168
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

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,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events