Create a Sub-task with status of parent issue (JIRA 7.7.1)

[Peter Ries]

Hi everybody.

I need to create a sub-task for a specific project with the status of the parent issue.

I already tried to use project automation but ended up with the status always being "TODO" after creation or getting an error like "Invalid transition" as there's no workflow jumping to the desired status.

Script runner may do it but I'm not able to write scripts and my google efforts were not successful.

Can anybody please provide this little script or a link to it?

Thanks!

[Petter Gonçalves · Accepted solution]

Hello Peter,

This functionality can be easily achieved using Automation for JIRA. You just need to configure the following rule:

Please, let me know if it works for you.

[Peter Ries]

Hi @Petter Gonçalves,

thanks for your input. I already tried this. I even checked the box under "More options..." -  "Bypass workflow conditions and permissions" but in result I get an error: 

--

Action details:

JQL CONDITION

The following issues passed:MT-418

TRANSITION ISSUE

No transitions to specified status could be found for issuesMT-418

--

After looking at the explaning text under "Destination Status" saying: "Ensure a transition from the issue's source status to your selected destination status exists." I think I'll have to create a workflow allowing any status when creating a subtask in this project.

I'll give it a try if our customer agrees.

[Petter Gonçalves]

Hello Peter,

Indeed, you will need to configure your sub-task workflow to allow transitions between any status to make it work since the parent issues can be in any status.

If you need further help customizing your workflow, please let me know.

[Deleted user]

Hi @Peter Ries,

Here is the link for the adaptavist scriptrunner with an example which helps you to inherit the parent summary. Hope this helps you.

you can also have a look at a Bobswift add-on create on transition, which needs only a simple postfunction configuration to create a subtask on a transition of an issue.

Regards,

Sravya

[Peter Ries]

Hi @[deleted]

thanks for your link. I already found this one as well, but got the same result as when I used the (much simpler) Project Automation (see Petterson's approach).

It seems as all approaches fail as long as there's no workflow allowing to jump to the desired destination status on create. Our customer's workflow only allows ToDo and Backlog when creating a ticket and this seems to supercede the status that project automation or any script tries to set.

BR

Peter