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,323,862
Community Members
 
Community Events
168
Community Groups

AUTOMATION, COPY THE SUBTASK TO THE ANOTHER PROJECT AND LINK IT WITH IT'S PARENT ISSUE

Edited

HELLO, I have a question about sub-task automation.

 

I already had made an automation that copys issue from project A to another project B and link(relate to) them each other(A and B).

 

1. Project A: Make "issue 1"

2. Project B: automatically make "clone-issue 1"

3. automatically relate "issue1(project A)" and "clone-issue 1(project B)"

 

And The question is

1. When I make a subtask in a issue1 (project A ), 

2. I want to automatically copy(clone) the clone-subtask in clone-issue 1(project B).

3. Of course the clone-subtask should have "clone-issue 1(project B)" as a parent.

 

Thank you.

Notes_210528_225307_1.jpg

3 answers

Hi there, is there a solution to this? I am experiencing the same situation as the original question!

I would like to be able to clone my subtasks from Project A to Project B (And all subsequent subtasks to be created in the future), while still maintaining hierarchy of the parent.

0 votes

If you're open to try a Marketplace app, you can have a look at our Jira cloud app Deep Clone for Jira.

It is possible to clone and move issues including their subtasks and keep their hierarchy with our Jira cloud app.

Among other advanced cloning functions, you can even filter, which substaks you want to clone (e.g. only open subtasks).

You can automate cloning by

- Either creating a Deep Clone workflow post-function

- Or integrate it with Jira Automation

If you have questions or feedback, don't hesitate to contact us.

deep-clone_clone_subtasks.png

0 votes

> When I make a subtask in a issue1 (project A ), I want to automatically copy(clone) the clone-subtask in clone-issue 1(project B).

Ok, then your automation or script should be triggered by "issue create"

> Of course the clone-subtask should have "clone-issue 1(project B)" as a parent.

How are you identifying the new parent issue?  You can't assume "if sub-task is on issue A-42, sub-task on B-42 - B-42 might not exist, or it might be numbered B-22 or B-213123".  You'll need to come up with a rule for finding the target and hope you can match them up!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

2,536 views 6 22
Read article

Atlassian Community Events