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

How to Automatically create Sub - task using script runner post function?

Srilatha Kolla

We have a requirement to be able to automatically create a few sub tasks, when an issue type called Feature is created. I have tried to use the script runner in post function of Submit. I do not see any sub task created after the feature being created.

I tried with having no specific criteria , when creating a sub task other than the Target Type being sub task. Didn't work either. Am I missing some thing?

Accepted answers

All comments

unknown

What troubleshooting have you done so far? Did you follow any document to create your script? Try following the instructions here in the JIRA ScriptRunner Built-in scripts.

Reference: https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html

Thanos Batagiannis _Adaptavist_

Hi Srillatha

Below is a sample custom script that you can use in order to create a number of subtasks.

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.customfields.manager.OptionsManager

def constantManager = ComponentAccessor.getConstantsManager()
def user = ComponentAccessor.getJiraAuthenticationContext().get
def issueFactory = ComponentAccessor.getIssueFactory()
def subTaskManager = ComponentAccessor.getSubTaskManager()
def issueManager = ComponentAccessor.getIssueManager()

Issue parentIssue = issue

if (parentIssue.getIssueTypeObject().getName() == 'Sub-task')
 return

if (parentIssue.getIssueTypeObject().name != 'Feature')
 return

def summariesList = ["Summary 1", "Summary 2", "Summary 3"]

// code in order to create the values to update a CascadingSelect custom field
def cascadingSelect = ComponentAccessor.customFieldManager.getCustomFieldObjectByName("CascadingSelect")
def fieldConfig = cascadingSelect?.getRelevantConfig(parentIssue)
def listOfOptions = ComponentAccessor.getComponent(OptionsManager).getOptions(fieldConfig)
def parentOption = listOfOptions?.find {it.value == "AAA"}
def childOption = parentOption?.getChildOptions()?.find {it.value == "A2"}

def mapWithValues = [:]
mapWithValues.put(null, parentOption)
mapWithValues.put('1', childOption)

summariesList.each {
 MutableIssue newSubTask = issueFactory.getIssue()
 newSubTask.setAssigneeId(parentIssue.assigneeId)
 newSubTask.setSummary(it)
 newSubTask.setParentObject(parentIssue)
 newSubTask.setProjectObject(parentIssue.getProjectObject())
 newSubTask.setIssueTypeId(constantManager.getAllIssueTypeObjects().find{
 it.getName() == "Sub-task"
 }.id)
 // Add any other fields you want for the newly created sub task
 newSubTask.setCustomFieldValue(cascadingSelect, mapWithValues)

 def newIssueParams = ["issue" : newSubTask] as Map<String,Object>

 //for JIRA v6.*
 issueManager.createIssueObject(user.directoryUser, newIssueParams)
 subTaskManager.createSubTaskIssueLink(parentIssue, newSubTask, user.directoryUser)
 // for JIRA v7.*
 issueManager.createIssueObject(user, newIssueParams)
 subTaskManager.createSubTaskIssueLink(parentIssue, newSubTask, user)

 log.info "Issue with summary ${newSubTask.summary} created"
}

Note. Add it as a post function -> script post function -> custom script post function and make sure this goes after the 'Creates the issue originally' action (because before that the issue doesn't really exist, unless you get it's values using the transientVars). Hope that helps.

PS. If you are in a JIRA v7.* then you will need the application user therefore use user instead of user.directoryUser

JamieA

Did you remember to publish the workflow?

If you want complete control you can use a script like the one @Thanos Batagiannis [Adaptavist] published above, although you should try to work out what the problem with the built-in script is first.

John River

Hi Thanos,

Any chance you could help me with this line:

Map&lt;String,Object&gt; newIssueParams = ["issue" : newSubTask] as Map&lt;String,Object&gt

It seems like it has been HTML formatted.

Thanos Batagiannis _Adaptavist_

Hey Shaw, I edited the snippet, now it should display the code fine.

John River

Thanks!

Dan27

Cancel the reply.

Chander Korshika

@Thanos Batagiannis _Adaptavist_ Can you help in modifying on of your script to Create Sub-Tasks based on Custom field value (numeric Value).

I want to create number of sub-tasks based on the field value of the custom field which would be filled at the time of ticket creation.

Thanks

Aarón López López

Hi @Chander Korshika I am trying the same thing and I think I am missing something

Can you give me an example?

Thank you.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

addon-com.onresolve.jira.groovy.groovyrunner