Copying default / custom fields from one subtask to another

[Michael]

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]

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

[Ste Wright]

Hi @Michael

How are you creating the sub-task during the transition? Is there an app you're using to enable this?

Knowing which app is in use now will help clarify if there's a solution it can cover - or if you need to use something else.

For example, we use Automation for Jira to do this - but you might have another app already :)

Ste

[Michael]

Hi @Ste Wright

Within the original subtask we are using JSU's "trigger a transition on the parent issue" post function which in-turn has a JSU post function of it's own called "created a linked issue".

Despite the name of the above JSU post function, one of the options within the "create a linked issue" allows for the creation of a subtask which is what we are using.

We do not want to used linked issues for this particular task because we want all tickets related to a parent ticket to be visible within the parent ticket page.

With that said, after we figure out how to copy these fields from the original subtask to the other, we would like to somehow automatically "link" the two subtask together with a "related" issue link so that people can see within both subtasks that they are related to each other and that they came from the same requester at the same time.

Does that help any?

Thanks,

~mike

[Ste Wright]

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

[Michael]

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