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

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. 

This would be super helpful when utilizing a Service Project to collect requests and a Software Project to perform tasks. We would like to collect the information through the form in the Service Project and then copy it to the Software Project. This should be standard.

We use forms for all of our Customer interactions.  As our organization has matured, we've added more and more teams to Jira.  One of the things that we need to do is transfer work to other teams (other projects tangentially related to the Service Desk, but our customers are trained to open issues).  We have a rule that clones the issue, but we can't move the form which makes it more difficult for those users to work on the reported issues.

You have a copy within the same project.  You have a move within the same project.

Why can't we copy and move between them?  It seems like a no brainer.

It is not useful if the form cannot be copied in cross projects. We were considering to use form for HR onboard employee request, but the form cannot be copied to the other auto-created linked tickets for IT teams in other projects, so it is meaningless to fill in the form, now we can only consider to create many custom fields.

Common Recurring JSM Client Use-Case | Creating a single, distributable (via Automation) document of truth (Jira Forms) for New Hire Onboarding to be originated from the HR Team and distributed to the IT, FAC, & ACT Projects.

So why have a 'copy form' option in the automation menu when it doesn't do the thing you want it to do?

It would really help us out between our different projects.

Ariëlle

Agree, this should be standard. We want to be able to attach a form from a service desk request to the newly created issue that becomes the "working" issue for our internal team on the project where we track resource and working hours required.

Thanks,

Rebecca

I think this would be pretty straight forward to implement: 

There is an manual move action for issues, which makes the form persist in another project

If you'd make this move action available as automation action it should be possible to move issues including the form to another project.

Are there any reasons to not make the move action available as automation?

If you really wanted to copy the issue to another project you would have to copy it first inside of the project and then use the move action on one of the issues.

Another solution would be to still make the copy form action available when the automation's scope is set to more than one project, but I don't know if this causes trouble somewhere else. 

I would love to see this feature so we our DevOps and Developers can hand each other issues with custom forms included via Workflow + Jira Automation

Thanks 

Tim

+1

This should be standard. The only reason I need this feature is because I'm trying to copy from one project to another.