Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

So excited to hear this is up for development. It's going to save a lot of headaches when automatically creating tasks in other projects. A lot of data is captured in a form so the idea of being able to copy the form into another project is welcome news indeed.

For those looking for a temporary work around. If you know your API, you can create a copy of the form template in the target project and then, using API, interrogate the source form fields and map them into the target form fields. It's rather messy, but it does work.

Hi everyone - a quick note to say that we have tentatively added this to our roadmap in the next 6-12 months. While we don't have exact dates yet, we understand its importance and will keep you updated on our progress.

Thanks,

Sam

JSM Principal Product Manager

We are in the same predicament as many others here, what is the latest on this enhancement?  There hasn't been an update in over a year? 3594564a659e 96677a1d9b4c 

Attempted to setup an automation rule today where I wanted to copy form to a newly generated issue in another project, that was actioned earlier in the rule. Would be great to be able to have this work! Cheers

This feature request is necessary for our business flow. Is there an update on when this will be implemented? 

We have scalability issues using API calls to extract data from forms. Apart from that, documenting the process to eradicate any single point of failure involves much technical knowledge and accuracy. Even the best document could be misunderstood. Therefore my company does not support using API calls with forms.

Sub-tasks or linked cases in other projects need the information captured in the Parent case's form.

It is essential, therefore, that and automation must be allowed to copy the form in its entirety to the sub-task in the secondary project.

As demand for A4J grows, this becomes an increasingly necessary feature for A4J—a must-have.

We really need this feature as forms are being heavily used in JSM and for some requests this information HAS to be forwarded onto any number of Jira Software projects. Really in a bind here as you can't "MOVE" an issue using automation. Can CLONE into another project, but it doesn't include the form.

Also - we're expecting another update in October? It will be November in < 3 hours.

If you think that one solution is to link the Service Management issue with the Software project one and then refer back to the form; you can't unless the person has an "Agent" JSM license. I'd have to give that license to many of our developers (impractical). 

FYI to all here, if you move the issue from a JSM project to a Software project the form will go with the issue. So you could clone the issue and move one just not be able to do it with automation. Just thought I would share my findings. 
This would be helpful to automation the issue to clone the form with the newly created issue to a software project for other teams to see the same data.