How to create a sub-task template in ScriptRunner Behaviours

Question

I installed Behaviours on our Jira cloud instance and was able to create creation templates for parent issue types, e.g. Story, etc. but that same functionality failed to work when trying the same on sub-tasks.

I could not find any information in the available information so I am raising a question here.

I hope it is simply a question of my not using the features correctly.

-Gérard Cattin

p.s. I am not looking for a ScriptRunner script to do that but for a Behaviours ScriptRunner solution.

Gerard Cattin · Answer

Hello Sean, thank you for your response. I have added feedback on that link above.

The other solution involves creating ScriptRunner scripts and we don't have developers to do that. I am an Atlassian Admin and I do that between my software release management tasks.

I was so excited when I discovered that Behaviours natively handled this long awaited feature of template creation, but felt a bit cheated, honestly, when I realized that it only did half of the job and skipped on the subtasks.

At the moment, the groups that are most upset are the testing engineers as they get penalized for lack of consistency across the board. Product owners gladly adopted the improved consistency when writing stories or epics given the Behaviours support for parent type issue types, but QA uses mostly sub-tasks. The devs also find themselves in somewhat the same predicament as they also get story subtasks. They can use the templates for Spikes and other type of parent cards so it is partial miss for them.

Implementing sub-tasks in Behaviours would really complete the feature and enable a true templatizing solution.

in any case, I am all ears for other solutions besides cloning cards which we have done since time immemorial.

Sean Chua _Adaptavist_ · Answer

Hey @Gerard Cattin ,

Behaviours currently can't do this for sub-task type. Do vote and follow the feedback/suggestion: https://scriptrunner-for-jira-cloud.nolt.io/103

What are you trying to do for the sub-task? Pre-fill details, update something etc?

Maybe something else can be done with the other ScriptRunner for Jira Cloud features as an alternative.