Creating multiple stories with subtasks from info in the main Epic

[Marcel Huisman]

We need to decommission 60+ Servers. I have an epic with a list of servernames.

I like to create stories in this epic each with its own subtasks because we have different colleagues doing tasks for the decommissioning of a server.

Is it possible to create these stories based on the list of servers in the description of an Epic.

I already have an automation to create the subtasks, but I need the 60+ Epics with name "Decommission {Servername from list Epic}"

[Hariharan Iyer · Accepted solution]

Hi @Marcel Huisman ,

Coincidentally I answered a similar question today :-). Yes this is possible using Automation as I've explained here - https://community.atlassian.com/t5/Jira-Service-Management/Create-Multiple-Issues-from-One-Paragraph-Multi-Line-Field/qaq-p/2603348#U2603897

In your case, I think the parent ticket is already created, so you can set the first condition to "Issue commented on" (and add a condition so it only executes for that one EPIC), and then just add a random comment.

Hope that helps!

[Marcel Huisman]

I think I need more help 😬

We are using Jira Software, not Jira Service management. I have a list of servers in the description of the main Epic with name "INF - Decommission Multiple Servers".

First, I will manually trigger the automation from the epic. But it will only run when the Epic name starts with "INF - Decommission Multiple".

 I need some help from the Advanced branching. Which smart value do I need to read the list of servers and how to create a subtask from this with that value in the name of this task.?

[Marcel Huisman]

I guess something like this (updated)? if I trigger it from the last comment with the list off Servers:



Is below correct is I want to create the Story in the main Epic? or do I need to specify the parent epic?

[Hariharan Iyer]

Hi @Marcel Huisman , glad to help!

Rules and smart values work pretty much the same way in JSM and Jira Software. So the smart value in advanced branching remains the same (you can change the variable name to "serverName" though). This is assuming the servers are listed line by line. If it's a different format, like a comma-separated list, you would have to change the separator in the smart value.

In the last step, you would create an issue of type Epic in project INF, and the summary would be 

Decommission {{serverName}}

 And you won't need anything in "Additional Fields" I guess.

[Marcel Huisman]

Sorry @Hariharan Iyer , I edited my previous comment. thought it would be better to list the servers in the comment field, so if I trigger on the last comment, I can add servers later. 

[Marcel Huisman]

does the split("\n" also work for this Smart Value?

[Hariharan Iyer]

Yes, this looks mostly correct. Just a couple of nits

1. The smart value should be issue.comments.last.body.split("\n"), not "issue.comment.last...".

2. In the second image, you can select "Epic Link" in the "Choose Fields to set..." selection, and then select your epic from the dropdown that comes up.

[Hariharan Iyer]

> so if I trigger on the last comment, I can add servers later. 

Yes, this seems like a good option. Then you can use the same Epic for servers that are to be decommissioned later as well.

[Hariharan Iyer]

> does the split("\n" also work for this Smart Value?

Yes, it would work for any multi-line string value.

[Marcel Huisman]

Thanks @Hariharan Iyer  instead of epic link, I need to use Parent right? And if I select Current Issue it will select the Parent Epic, or is this an incorrect assumption? 

[Marcel Huisman · Accepted solution]

Thanks, Hariharan, I will try this..