How to add custom imports to 'Create sub-task'?


I'm using the 'Create sub-task' option in this exceptional tool, but I have a problem referring to my constants 'CustomFields' class.

When this code is triggered:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.fields.CustomField
import org.apache.log4j.*
import groovy.util.logging.*
import static*

def Logger log = Logger.getInstance(getClass())
log.level = Level.debug "Workflow - In Progress - Create QA sub-task"
CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()
CustomField cfQaRequiredYN = customFieldManager.getCustomFieldObject(CFQAREQUIREDYN) "QA Required = ${issue.getCustomFieldValue(cfQaRequiredYN)}" == 'Story' && ((issue.getCustomFieldValue(cfQaRequiredYN).toString() ?: "").equals("Yes"))

it logs these two errors in the log file:

cript4.groovy: 6: unable to resolve class
 @ line 6, column 1.
   import static*
Script4.groovy: 6: unable to resolve class
 @ line 6, column 1.
   import static*
2 errors

The answer to my earlier 'ScriptRunner Primer' question works perfectly for scripts, but the Create Sub-task 'script-lit' won't work with this.

Being able to refer to the custom fields by constants makes the deployment to another instance easier as its only a single place to update. Is this possible with the 'Create sub-task' function?

Kind regards,


2 answers

1 accepted

0 votes
Accepted answer

Answering my own last question: - adding '(CreateSubTask.Field_SubTask_Action) : 1' does the trick am

issue : issue,
(CreateSubTask.FIELD_TARGET_ISSUE_TYPE) : constantsManager.getSubTaskIssueTypeObjects().find { == ITYPE_QASUBTASK }.id.toString(),
(CreateSubTask.FIELD_SUBTASK_SUMMARY) : "New QA Sub-task - please update",
(CreateSubTask.FIELD_SUBTASK_ACTION) : 1 // Step ID for Open

Unfortunately that doesn't work - this is The reasons why are a bit dull, but when you point to a file it's executed by a GroovyScriptEngine, when it's an inline script it's the groovy javax.script.ScriptEngine, and the two have different capabilities. This is something I need to get to.

You can work around it by using a custom script post-function, and just calling the CreateSubTask built-in script, like this. It's not totally satisfactory but it works, and it's better than duplicating your constants around.

package ...

import com.atlassian.jira.component.ComponentAccessor
import com.onresolve.scriptrunner.canned.jira.workflow.postfunctions.CreateSubTask

// all your condition code here...
def conditionPasses = true

def constantsManager = ComponentAccessor.getConstantsManager()
if (conditionPasses) {
    def createSubTask = new CreateSubTask()
        issue                                  : issue,
        (CreateSubTask.FIELD_TARGET_ISSUE_TYPE): constantsManager.getSubTaskIssueTypeObjects().find {
   == "Sub-task"
        (CreateSubTask.FIELD_SUBTASK_SUMMARY)  : "some summary",

Hi Jamie Many thanks for the prompt reply. I'll implement that solution and keep the information for future reference. Cheers Richard

Thanks - I was able to implement this today. But I now have a related question - which parameters do I set ask it to reopen any existing matching sub-tasks rather than create new ones?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 07, 2019 in Marketplace Apps

A Timeless Love Story

It started as any story starts, on a normal, rainy day.   Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...

457 views 8 27
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you