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

Jira Workflow Toolbox - Create Subtask - Initial Try outs

KRC

We are evaluating JWT add on. We want to create subtask when a parent is created. We want to use post function on create transition on parent. We want to create 6 subtasks with due date in and a cascading field(for each subtask due date will be same but cascading filed parent and child will change) either we want to use one post function to set 6 subtasks or 6 post functions for 6 subtasks.

we tried setting cascading field and due date by SET Fields. and no luck. can anyone guide how to set these two fields?

Accepted answers

Thorsten Letschert _Decadis AG_

Hi @KRC,

you're able to include everything in just one post function.

I'll provide you with an example with 3 subtasks - but you can easily alter that to 6.

My cascading select list options look like this:

In your Create issues and subtasks post function you have to enter the following configuration:

Issues to be created: Multiple issues based on Math Expression followed by the number of subtasks you want to create (in my example I entered 3)
Issue Type: Your subtask issue type
Parent Issue: Current Issue

In the fields which follow you can use this expression to point to your subtasks:

getMatchingValue(^, [1,2,3], ["Option for subtask #1", "Option for subtask #2", "Option for subtask #3"])

To set a cascading select list you have to provide the field value in this format:

"ParentOption,ChildOption" // the comma is important

In my example the configuration for my field named CF Select List (cascading) looked like this:

getMatchingValue(^, [1,2,3], ["Level 1A,Level 2A", "Level 1A,Level 2B", "Level 1B,"])

Together with a dynamic summary configured the same way, the result after creating my issue named Subtask Testing then looks like this:

Is your due date a fix value or do you want to push the date entered within the parent issue?

Cheers,

Thorsten

All comments

Thorsten Letschert _Decadis AG_

Hi @KRC,

you're able to include everything in just one post function.

I'll provide you with an example with 3 subtasks - but you can easily alter that to 6.

My cascading select list options look like this:

In your Create issues and subtasks post function you have to enter the following configuration:

Issues to be created: Multiple issues based on Math Expression followed by the number of subtasks you want to create (in my example I entered 3)
Issue Type: Your subtask issue type
Parent Issue: Current Issue

In the fields which follow you can use this expression to point to your subtasks:

getMatchingValue(^, [1,2,3], ["Option for subtask #1", "Option for subtask #2", "Option for subtask #3"])

To set a cascading select list you have to provide the field value in this format:

"ParentOption,ChildOption" // the comma is important

In my example the configuration for my field named CF Select List (cascading) looked like this:

getMatchingValue(^, [1,2,3], ["Level 1A,Level 2A", "Level 1A,Level 2B", "Level 1B,"])

Together with a dynamic summary configured the same way, the result after creating my issue named Subtask Testing then looks like this:

Is your due date a fix value or do you want to push the date entered within the parent issue?

Cheers,

Thorsten

Thorsten Letschert _Decadis AG_

Just to be sure: if you want to create 6 issues, your expression should look like this of course:

getMatchingValue(^, [1,2,3,4,5,6], ["Option for subtask #1", etc.])

KRC

@Thorsten Letschert _Decadis AG_ Due date is a fixed value. Will try your suggested example and let you know. Thank you for the reply.

KRC

In your example, where do you set cascading field something like %{1234}

Abinash Satapathy

Hello @Thorsten Letschert _Decadis AG_ ,

Thanks for the Solution.

I have one query.

If you need to assign above created sub tasks ( let's say 3 sub tasks to 3 different users automatically ) then How to achieve that .

Thanks in Advance.

Abinash

Thorsten Letschert _Decadis AG_

Hi @Abinash Satapathy,

just add the Assignee field in the Set Fields section and configure as follows:

Value type: Parsed text (advanced mode)

Text to be parsed:

getMatchingValue(^,[1,2,3],["userNameAssignee1","userNameAssignee2","userNameAssignee3"])

Cheers,
Thorsten

Abinash Satapathy

Thanks a lot

Abinash Satapathy

Hello Thorsten Letschert ,

I want to fill Due date automatically based on a rule.

For ex: If Issue is created in the Month of August then Due Date will be 3rd Of Next Month i.e 3rd September.

In general Due date should be 3rd of Next Month

Can it be achieved ?

Thanks in Advance.

Regards,
Abinash

Thorsten Letschert _Decadis AG_

Hi @Abinash Satapathy,

this is possible with the help of JWT as well. However, would you mind opening a new question since this is clearly a quite different topic?

Cheers,
Thorsten

Abinash Satapathy

Hi @Thorsten Letschert _Decadis AG_ ,

Thanks for answering back .

I have figured out way to achieve my goal .

Thanks to JWT add on .

Cheers and Regards,
Abinash

Floyd Goodell

Hello @Thorsten Letschert _Decadis AG_ Thank you for this thread it was incredibly useful.

Is there a way to insert the parent issue number into the sub task summary?

Using your example above the end goal would be something like "App 26 Summary 1, App 26 Summary 2, etc"

Or even better include the Summary of the parent issue, Subtask Testing Summary 1 for example.

I wanted to try to make it a little more clear for my users what the parent issue was for the subtask they had assigned to them in an email notification.

Welcome!

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

Quick Links

Find more posts tagged with

jira

addon-com.fca.jira.plugins.workflowtoolbox.workflow-toolbox