Copying default / custom fields from one subtask to another

Question

hello everyone,

Within our current workflow, we have a subtask which creates a new subtask off the parent ticket during a transition.

We want to copy specific field values from the original  subtask to the new subtask while it's being created, but we currently can't figure out how to "link" the two subtask fields together.

We are running the data center version of Jira 8.8. If anyone can help us out, we would be extremely greatful!

Partibha Rani · Answer

Hi Michael,

Currently this is possible with a workaround solution. You can divide it into two post-functions, Create linked issue and Copy Value Post-function. Fields you want to copy from the sub-task can be put in Copy Value fields Post-function with JQL scope, Query could be: parent = {issue.key}. If there are already multiple sub-tasks than put something unique in the query from which you want to copy otherwise just put Max issues found 1.

For more detailed information, please contact to our support  https://servicedesk-apps.beecom.ch/servicedesk/customer/portal/3 or Email us on apps@beecom.ch

Regards

Partibha Rani

Michael_qy22gs · Answer

Hi again @Ste Wright

unfortunately, we've already looked into that and all other support pages within the vendor's wiki. Those copy-able fields are only available for the parent ticket and the subtask ticket it is copying to; and not any other subtasks within the same parent ticket.

Automation for Jira is a paid for service and a very expensive one at that, which is a no go on our end :(  .

Do you know of any groovy scripting that might help us out here, or anyone who has deep knowledge of groovy scripts which might be able to help us out here?

Thanks,
~Mike

Ste Wright · Answer

Hi @Michael

It's not an app we use - but I found this support page on the vendor's wiki which suggests you can copy field values from the origin issue to the new one (or set new values entirely)

I would see if this can set the linked issue and required fields you need.

If this isn't possible, you might need to consider using a separate app - as I say, we use Automation for Jira. I gave this a go and got linked issues to work.

Ste