Automatically create a linked story when moving an Epic into the "In Progress" status

[Heather Millar]

This is more a theoretical question than an issue. I may be being over ambitious!

I'd like to be able to set up automation to create the following steps;

1. Epic moves from "Ready" status to "In Progress"

2. A linked Story ticket is automatically created in a specific project (not the same one the Epic is in, but it will always be that same project)

3. The new Story uses the same Summary as the Epic, ideally with an added prefix of "Document: "

4. A "Component" or similar field data is also carried into the new ticket

A little overview of what I'm trying to do, We want to ensure that the documentation team is notified that a new Epic (project/feature) has been created so that it feeds into the relevant sprints and doesn't get missed. This will be a new addition to the existing workflow (documentation has never been included at the start of a project previously, they just catch up when things are completed) so we're trying to automate the starting steps so that things don't get missed at the beginning of this change in workflow.

Thanks in advance!

[Ezgi Bayındır · Accepted solution]

Hi @Heather Millar ,

Welcome to community!

I created an automation rule by looking your explanation.

In the summary field, use the {{triggerIssue.summary}} field to copy the summary of the newly created story from epic. Also use {{triggerIssue.key}} for Epic Link, in this way, new story will be linked to epic. 

Also you should check this link for discover Jira Automation Jira Automation | Atlassian

Best,

Ezgi

[Heather Millar]

Thanks Ezgi, I think this will do what we need!

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi Heather,

Thank you for your question.

I can confirm thaty the ScriptRunner for Jira Cloud plugin could help to achieve your requirement.

Using ScriptRunner you could a post function tp the transition that transitions the issue from the Ready Status to the In Progress status and have this create the issue and a link to it.

I have some sample code here that shows how to do this that could be used as a guide to help create the script that you require. 

In this example you can set the project Key for the project should be creted in inside the projectKey Variable.

You can then update the createIssue rest api call starting on line 23 to set the summary of the issue by getting the summary of the current issue and a prefix of document to the start of it by changing line 18 for the newSummary variabke to be similar to "Document" + issue.fields.summary.

You can then also set the component on the new issue inside the createIssue rest api call and we have an example of setting a component here that shows how to do this.

I hope this information helps.

Regards,

Kristian

[Heather Millar]

Thanks Kristian, I will check if we have that plugin.