I have a project with a pretty complex workflow. The project admin would like to use subtasks to track the many steps for a given task. This results in upwards of 30 subtasks per task.
My goal is to provide a manual trigger for the user that will generate the standard subtasks on the particular issue that is selected. I've gotten close but not quite where I want to be.
I created a template issue (PM-716) whose entire purpose is to house the sample subtasks. I can look up the sub-tasks then create a new issue for each and specify which fields to populate, but ideally, I would like to clone the issues and ALL fields. My current solution works for now, but any help would be appreciated.
There's an approach that might work for you discussed here:
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Brock Jolet
You could try using clone issue on each subtask, and then call the REST API to change the parent, as described in the work-around for this suggestion: https://jira.atlassian.com/browse/JSWCLOUD-22718
Please note that with the number of subtasks you have described, to support your workflow, this will be a very slow rule and could lead to other problems/unintended consequences.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Bill! I'll try this out to see if it works for my situation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.