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; } } }

Creating a sub-task automatically when moving a card between different lanes on the jira board

Anand_at05su

I am looking to automate the incident creation process in JIRA for the QAs. Currently the QAs move the card (story) from "Testing" lane to "Development" lane if there is an issue with the card, commenting on the original card (story). However with this approach, any incidents/bugs aren't trackable/traceable hence prefer to create an incident/bug subtask for every time an issue is found during testing for a story. Moreover, due to the heavy administration with creating incidents as a subtask everytime, I would like to explore if this can be automated. Is there anyway to automate this in the JIRA?

Accepted answers

Trudy P Claspill

Hello @Anand

Welcome to the community.

When you say the issue is moving from one "lane" to another, are you talking about changing the status of the issue?

When you are talking about automating the creation of a subtask, what exactly would you expect the content of the subtask to be (the Summary and Description, specifically) and where would that content come from?

Is your JIRA environment on premise or are you using JIRA Cloud?

If you are using JIRA Cloud there is a native feature called Automation that can be used to automate creation of issues based on conditions.

If you are using JIRA Server, Automaton for JIRA is not native and you would have to buy the app and add it to your server.

https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?tab=overview&hosting=server

There are other apps that might be useful, but also might have more functionality than you need and therefore may be too expensive.

All comments

Trudy P Claspill

Hello @Anand

Welcome to the community.

When you say the issue is moving from one "lane" to another, are you talking about changing the status of the issue?

Is your JIRA environment on premise or are you using JIRA Cloud?

If you are using JIRA Cloud there is a native feature called Automation that can be used to automate creation of issues based on conditions.

If you are using JIRA Server, Automaton for JIRA is not native and you would have to buy the app and add it to your server.

https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?tab=overview&hosting=server

There are other apps that might be useful, but also might have more functionality than you need and therefore may be too expensive.

Anand_at05su

When you say the issue is moving from one "lane" to another, are you talking about changing the status of the issue?

Yes, the status of the card moves from "Testing" back to "Development"

When you are talking about automating the creation of a subtask, what exactly would you expect the content of the subtask to be (the Summary and Description, specifically) and where would that content come from?

I am thinking some kind of an incident template in the description and summary with Bug-<uuid>. The card once created, QA will open the card and fill in the relevant details.

If you are using JIRA Server, Automaton for JIRA is not native and you would have to buy the app and add it to your server.

We host our own Jira server.

Trudy P Claspill

Adding a Listener to create the subtask when the transition occurs might be an option.

https://confluence.atlassian.com/adminjiraserver/listeners-938846909.html

When I last worked with JIRA Server, we had an app called Adaptavist ScriptRunner that I believe extended the functionality of Listeners, so I'm not sure what all can be done with the native Listener functionality.

The type of automation you describe (the incident template) is something that could be done with Automation for JIRA.

Anand_at05su

Thanks Trudy! Looks like we got "Automate for Jira" installed in the server. As you said, looks like it can do the job for me. Thankyou for your help.