Automating multiple stories with sub-tasks

[philipf]

Hello,

I have been trying to clone an epic with multiple stories, and then each story has multiple sub-tasks. 

I have give up cloning the epic, and just now want to automate stories every month to then next to a year long parent.

This will work, all good.

My problem is now when I go to create new stories and then sub-tasks. It asks for a jwl query which I try to use labels, and it tells me the projects aren't setup for it. I did make sure the project had the label field and the actual label created, but no dice.

So was looking for advice on how I can. Create automated stories, with sub-tasks. But the kicker is that each story goes into a different board. Meaning the epic/parent is in project A, the story and sub-tasks are in project B, C, and D.

Can I even create multiple stories with sub-tasks using branches?

[Bill Sheboy · Accepted solution]

Hi @philipf 

There is a lot going on in your question, so if I miss something, please let me know...

The error you noted about a JQL query seems to indicate the scheduled trigger had no JQL (and thus no issues) but your rule is referencing "Current Issue" in a branch.  That will not work.

How do you identify the issues you want to clone: by some query, manually, something else?

Next, you asked:

Can I even create multiple stories with sub-tasks using branches?

Yes, but not in one automation rule.  The reasons why are:

• Branches cannot be nested (e.g., branch to clone stories and inside is a branch to clone subtask)
• Branches on more-than-one-thing get processed in parallel and asynchronously.  And so the first branch to clone the stories may not complete before a branch after that in the rule tries to handle the subtasks.

This is why this scenario is often handled using the built-in Clone function or marketplace addons, which use other programming tools to clone the issues correctly.

It may be possible to clone issues and their subtasks using multiple automation rules, although it is error prone because any rule failures, timing problems, or Atlassian outages will break the chain.

Kind regards,
Bill

[Luka Hummel - codefortynine]

Hi @philipf

If you are willing to try a third-party app, you could try our app Deep Clone for Jira. Deep Clone allows you to clone issues, including epics, stories, and sub-tasks, and move them to different projects and boards. It offers advanced cloning options that can help automate your process. Here's how it can be relevant to your needs:

• Cross-project Cloning: Deep Clone allows you to clone issues (like stories and sub-tasks) to different projects. This should help you in distributing your stories and their corresponding sub-tasks across projects A, B, C, and D as required.
• Bulk Cloning: You can clone multiple issues at once, which is useful for handling numerous stories and sub-tasks simultaneously, saving time and effort.
• Custom Field and Label Handling: Deep Clone supports cloning of custom fields and labels, which can help in maintaining consistency across your cloned issues.
• Automated Cloning: While Deep Clone primarily focuses on manual cloning, it's possible to set up some level of automation. For instance, you can create a 'template' issue with all the necessary fields, labels, and configurations, and then use Deep Clone and a Jira automation to replicate this issue as needed.

[philipf]

I am trying deep clone.

Looks cool, but when I clone tickets in other projects, it kicks them into the project the epic is in, (which is different from the stories). 

So for me defeats the purpose currently when I have to go and move tickets within the epic.

[Luka Hummel - codefortynine]

Hi @philipf

Interesting. Can you share what you mean by 'kicks'? If you have selected Keep link to original parent under Epic/Parent link issues you have cloned to other projects should still have the Epic in the original project as a parent.

[philipf]

Thanks Bill, 

Sorry for my confused message, but you saw through it. 

I will consider multiple automation or a clone device.