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 can I allow the user to manually trigger the creation of multiple subtasks for an issue?

Rick Trudeau

I'm interested in a way of allowing users to automatically create multiple subtasks for an issue, but only if the user manually triggers it.

In my case, I don't want the subtasks automatically created when the issue is created. Instead, I want the user to drive the creation only if he wants the subtasks. So, for instance, if the parent issue had a new button/menu item that the user could press to trigger the auto-creation of the subtasks, that would be ideal.

Since I want this to be user driven, I don't want to trigger the auto-create function off a transition.

Any clues on how to integrate a script that would allow this via user driven interface?

Accepted answers

Bob Swift

See my comment on the other question you posted

All comments

Bob Swift

See my comment on the other question you posted

Rick Trudeau

Thanks Bob, and or the sake of completeness, I'll post your answer here:

"You can have a transition that does not actually change the state and associate any post functions you like including create on transition plugin post function to add one or more subtasks"

So if I understand your suggestion correctly, I would create a workflow transition from State1 to State1, and bind a post function to it that would trigger the creation of the subtasks. That way a user could select the transition from the menu and have the tasks auto-created?

Bob Swift

Yes. A create sub task post function for each subtask you want.

Rick Trudeau

Yes, thanks again. I think that will work.

One gotcha I'm running into is that when creating the subtask I want to copy to it some custom field values from the parent issue. What I'm finding is that when I try to get to the parent object from within the subTask post function context, I get a null returned. I'm guessing that the binding of the parent to the subTask probably isn't complete until after the subTask is created?

So maybe I need a primary post function to first create the subtask and then a secondary post function to go and modify the created subtask?