Attaching original completed form to newly spawned ticket?

[Jared Grywacheski]

We have an automation where when specific checkboxes are selected within a request type form additional tickets are created. 

I have this working properly but have just realized that when the form is attached to the newly created ticket it's attaching a brand new uncompleted form rather than the  completed form from the original parent ticket. It is possible to do this?

Please see the automation being used:

[Trudy Claspill]

Hello @Jared Grywacheski 

Doing a little research in the forum I found two references that might be helpful to you.

1. Copy a Form to the same project and for different projects using Automation and API 

2. Attaching the complete form as a PDF, and copying the PDF to the new issue.

[Jared Grywacheski]

Thanks @Trudy Claspill , creating a PDF of the form, then using the automation of "Choose fields to set..." and selecting attachments attaches the PDF version of the form to the newly created ticket. 

The issue now is that within that original form there is a section where the reported attaches an additional doc file. That doc file appears as an additional attachment to the original ticket but for some reason does not get copied over to the newly created ticket. 

Any ideas? 

[Trudy Claspill]

Please provide screen images of your current automation rule.

[Jared Grywacheski]

So within the original form from the top of the automation there is two checkboxes, if either of those checkboxes gets checked a new ticket is spawned (I have two identical automations, one for each checkbox)
I have turned on the option to turn that original form into a PDF and attach to the original ticket. Then within the Create a new I have it set to copy attachment from Current issue. 

The problem being that within that original form there is also a section where the reporter attaches a document and this document gets added as an attachment to the original ticket, but even with Copy attachment from Current issue it's only copying the PDF attachment of the form and not the file that was also attached to the form. 

[Trudy Claspill]

It is possible that the automation rule is firing before the attachment of the form's attachment has completed. Before the Create Issue action try inserting a Re-fetch Issue Data action.

[Jared Grywacheski]

Unfortunately that does not seem to do the trick which is odd given that both the PDF version of the form and the attached doc file both have the same attach timestamp on the parent ticket. 

[Trudy Claspill]

I'll have to do some research and experimentation and get back to you. I'm not as familiar with JSM Forms functionality as I am with other aspects of Jira/JSM.