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

Automatic subtask status change depending on previous subtask status

Germain Vincent

Hi everybody,

context: JIRA 7.2.0 and ScriptRunner. Not allowed to install more plugin. 2 worflows, one for the parent and one workflow dedicated to subtasks.

I'm new to JIRA and my company ask me to create post script functions that could be able to automatically change the status of subtasks or parents on specific conditions.

More specifically:

While the parent ticket is on "Open" status, user can create as many qualification subtasks as he wants/needs.

When all qualification subtasks are created, user can use the "start qualification" transition. This will change the parent status from "OPEN" to "Qualification in progress" and the status of the first subtask of the list from "Waiting" to "To do".

My first question is: Which script would you use to do that?

Then, I must add a post script function on the transition "Close subtask" that set the subtask status from "In progress" to "Closed" which will automatically change the status of the next subtask from "Waiting" to "To do".

Have you any idea on how I could manage that?

Thanks in advance.

Regards,

Accepted answers

Tarun Sapra

Hi Germain,

When user "clicks" on the "start qualification" to transition the parent from "open" to "qualification in progress" then to transition the first sub-task, you can see complete code sample here - https://community.atlassian.com/t5/Atlassian-Marketplace-questions/Groovy-Script-for-auto-transition-of-Subtask-which-can-be/qaq-p/152675

You can write a similar script to transition to transition the "next subtask" from "waiting" to "to do"

All comments

Tarun Sapra

Hi Germain,

You can write a similar script to transition to transition the "next subtask" from "waiting" to "to do"

Germain Vincent

Thanks a lot Tarun, I will have a look on that!

Germain Vincent

Tarun,

The link is not working. But I found the topic by searching through Atlassian. Thank you.

If I copy/paste th code in my JIRA I got a lot of unknown method error as you can see in the screenshot

I also copy/paste all the needed imports.

Do you have any idea why not working in my context?

Sorry, I'm a real beginner...

Tarun Sapra

Hello Germain,

Can you please post the code on gist.github.com and share here, it seems you are missing some import statements.

Germain Vincent

Hi Tarun,

Someone in my company helped me finding a different solution.

Comments are in French.

I also added a function that allow to change subtasks's status only if they share a "Lot" number.

Thanks for all your helps!

//Imports nécessaires
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.issue.IssueInputParametersImpl
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.config.SubTaskManager
import com.atlassian.jira.workflow.WorkflowTransitionUtil
import com.atlassian.jira.workflow.WorkflowTransitionUtilImpl
import com.atlassian.jira.util.JiraUtils
import com.opensymphony.workflow.WorkflowContext
import com.atlassian.jira.issue.customfields.manager.OptionsManager

//Création des variables et des différentes classes
def constantManager = ComponentAccessor.getConstantsManager()
def issueService = ComponentAccessor.getIssueService()
def cwdUser = ComponentAccessor.jiraAuthenticationContext.getLoggedInUser()
def issueManager = ComponentAccessor.getIssueManager()
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def componentManager = ComponentManager.instance
def optionsManager = ComponentManager.getComponentInstanceOfType(OptionsManager.class)
def subTaskManager = ComponentAccessor.getSubTaskManager()
//Variable permettant de rentrer et de sortir de la boucle "each"
def eachExit=0

//Récupération de la valeur du champ "Lot" de la sous-tâche affectée par la transition "CLOSE"
def Lot = customFieldManager.getCustomFieldObject("customfield_12604")
String LotValue = issue.getCustomFieldValue(Lot)

//Création de la collection de sous-tâches
MutableIssue parentIssue = issue.getParentObject() as MutableIssue
Collection subTasks = parentIssue.getSubTaskObjects()

//Si sous-tâches existantes
if (subTaskManager.subTasksEnabled && !subTasks.empty)
{
    //On parcourt la collection de sous-tâches
   subTasks.each
    {
        Issue it ->
        //Récupération de la valeur du champ "Lot" de chaque sous-tâches de la collection
        def Lot2 = customFieldManager.getCustomFieldObject("customfield_12604")
        String LotValue2 = it.getCustomFieldValue(Lot2)
        //Lorsque l'on rencontre une sous-tâche de la collection ayant un statut "En attente" et portant le même numéro de lot que la sous-tâche affectée par la transition "CLOSE"
       if(it.getStatus()?.name == 'En attente' && eachExit==0 && LotValue == LotValue2)
        {
           def issueInputParameters = new IssueInputParametersImpl()
           def transitionValidationResult = issueService.validateTransition(cwdUser, it.id, 711, issueInputParameters)
            //Afin de ne modifier l'état que de la première sous-tâche en statut "En attente" on arrête de balayer la collection en implémentant la variable
           eachExit=1
            //On fait évoluer le statut de la sous-tâche en "To do"
           if (transitionValidationResult.isValid())
            {
               issueService.transition(cwdUser, transitionValidationResult)
            }
        }
    }
}

Tarun Sapra_2ab78x

But what exactly was the issue?

Germain Vincent

Even my colleague was not able to find the issue.

So he gave me a code he wrotes a few times ago that was doing nearly the same I was expecting.

I just adapted the code to my context.

Sorry, I can't tell you what was not working with your solution in my context.

Anyway, thanks a lot, your help was really helpfull and even it was not perfectly working at the end (my fault) I learned a lot from you!

See you.

Germain

Welcome!

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

Quick Links

Find more posts tagged with

jira

transition

automation

status

sub-task