nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create a story including subtasks in another backlog when a story is done using automation.

Maarten Verreck

I have created an automation in backlo A that creates a story in backlog B when a story in backlog A is set to done.
The story is created and all the fields and smart values are created in backlog B.

But...

I red that it's not possible to create a set of subtasks for that story in this automation.

So I'm trying to create this in backlog B.

I already have an automation in place for creating subtasks when we create a story manualy in backlog B.

Somehow the trigger based on create story doesn't work when automation does this from another backlog.

What trigger should I use for this action?

Accepted answers

Valerie Knapp_gp7rpj

Hi @Maarten Verreck , thanks for your post.

Please can you share some screens of these automations with us? It is hard to offer advice without actually seeing what you are trying to do / how you are trying to do it.

It sounds like maybe the issue is this - that you haven't enabled the second automation to be called by the first

https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180

but it is hard to tell without seeing your rules.

Please provide more information so we can help.

Best wishes

All comments

Valerie Knapp_gp7rpj

Hi @Maarten Verreck , thanks for your post.

Please can you share some screens of these automations with us? It is hard to offer advice without actually seeing what you are trying to do / how you are trying to do it.

It sounds like maybe the issue is this - that you haven't enabled the second automation to be called by the first

https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180

but it is hard to tell without seeing your rules.

Please provide more information so we can help.

Best wishes

Taliah15

Use the "Issue created" trigger in backlog B for the subtask-creation automation. Ensure filtering or conditions are set if needed, as this trigger does fire for issues created by other automations as well, not only manual ones. @Maarten Verreck If this helps kindly let me know.

Maarten Verreck

In backlog A I have build an automation to create a story in backlog B
story to another backlog 1.png

In backlog B I created an automation that should create a subtask when a story has a creator that equals Automation for Jira.
Somehow a story that is created by automation is not seen as a created workitem.
story to another backlog 2.png

I use the automation below in most of my backlogs to add subtasks when I create a story or bug. This rule workes perfect. story to another backlog 3.png

Maarten Verreck

@Valerie Knapp Your suggestion works. I checked the option to be triggered by another automation and now the subtask is added.
I also got an error, but that one I can solve. THX

Olga Cheban _TitanApps_

hi @Maarten Verreck !

I see you already got the answer to your question, but I'd like to add that there is a simpler and more straightforward way to create a set of parent tasks + subtasks in another backlog / project. If you are open to trying out third-party apps, I can recommend our solution, Smart Templates for Jira.

It allows you to save any set of work items as a reusable template - regardless of how complex the hierarchy is. Then, you can generate the whole set of work items with just one button or use it with the native Automation for Jira. In the latter case, you will only need one rule as the whole set of tasks, including subtasks, will be created from one template.

You can save a template as Global - then, it will be available across all projects in your Jira instance. Additionally, Smart Templates support variables and scheduled work item creation.

Here's an example of such a template - a work item hierarchy consisting of an epic with tasks and checklists. It can also include subtasks and any custom hierarchy levels you have (such as themes and initiatives).

Test Case Template For Recurring Testing.png

I hope it's useful to learn about this simpler option. Please let me know if you have any questions!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-automation