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

Automation to copy description from one subtask to another in same parent task



I am looking to find information on how to copy the description from one subtask to another within the same parent task. 

Little background. We are automating the creation of subtasks using JSON. This data is imported into Jira and creates the subtasks but also provides the relevant URL and additional information in the description of each subtask (URL and information is different for each subtask).

How could I have a single subtask that could copy the description from each subtask created through the JSON data and house all of the URL and additional information within it?

1 answer

1 accepted

0 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

Hi @Jeremy Branby and welcome to the community!

If I'm understanding correctly, you're trying to create a sub-task that will continuously concatenate the Description field from JSON generated sub-tasks.

If I'm correct, this could work like this:

First, you'd need to leverage some type of tag (label, component, custom field) to differentiate the aggregate sub-task from the ones created by JSON.  I'll use a component called "Master" for my example:

  • TRIGGER: Issue Created
  • CONDITION: Issue Type = Sub-Task
  • CONDITION: Component NOT IN Master
    • Parent = {{issue.Parent}} AND Component IN (Master)
    • ACTION: Edit Issue (Description)
      • {{issue.Description}}\\ ---- \\{{triggerIssue.Description}}

This will trigger any time a new sub-task is created where the component is not Master.  Then searches for the Master sub-task and appends the new sub-task description at the bottom. \\ ---- \\  should separate descriptions with a horizontal line.

Hi Mark, 

Thank you for the suggestion, I tested this out and it was able to work. Thank you!!

Like Mark Segall likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events