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

Append Sub-task Comment to Parent Custom field

Im looking to see if we can append the comment of multiple sub-tasks into a parent custom field?  At the moment im able to set the Custom field value but it overwrites the previous comments  value in this custom field.  

Our use case.

We start with a story and once its transitioned to a specific status we create about 8 sub-tasks for each team that needs to review and approve or reject the change.

When a user add's a comment to the sub-task on the reject or approval screen and the story is in a specific status, we want to copy that last comment to a custom field on the parent to capture the reason for the approval or rejection

I was able to get the automation rule working, but each time a comment is added, it overwrites the previous one.  Is there a way to append the comment to the custom field or will it always overwrite the previous one?  We are on jira cloud, no script runner, we have JMWE but would like to use automation rule if possible.

Current Rule:



1 answer

1 accepted

0 votes
Answer accepted
Hana Kučerová Community Leader Jul 28, 2021

Hi @Julian Governale ,

please try to add

{{issue.Feasibility Study Summary}}

before --- to the Feasibility Study Summary field

{{issue.Feasibility Study Summary}}

@Hana Kučerová  Thank you so much for the quick response.  that did the trick and its now working as expected! 

Like Hana Kučerová likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events