Can forms for Jira Software be copied and shared with other Jira Software projects?

[Katrina Lieber]

Hi All, Public forms for Jira Software is relatively new per this release in April of 2025: https://support.atlassian.com/jira-software-cloud/docs/collect-information-for-your-team-with-a-form/?utm_source=sfmc&utm_medium=email&utm_campaign=EML-19985&jobid=107031956&subid=1906513144

While I'm excited about this release and have tested out the feature, I realized there was no great way to copy and share a form template from one project to another. It seems all forms need to be created from scratch within each project. I understand the need for forms to have a unique identifier associated with a specific project so work items created from forms are created in the desired project but not allowing the creation of form templates to be shared bewtween Jira software projects is rather cumbersome and not streamlined for scalability.


I know Jira Service Management has the ability to copy forms to other projects but it seems this is not yet a feature for forms in Jira Software projects. Does anyone know if this is on the product roadmap for Jira Software?

[John Funk]

Hi Katrina - Welcome to the Atlassian Community!

The short answer is no, Jira Software forms cannot currently be copied or shared across projects like you can with JSM. And there are no immediate plans to introduce JSM style forms to Jira Software projects. 

[Olha Yevdokymova_SaaSJet]

Hi @Katrina Lieber 

Hi! Thanks for bringing this up — it’s a common frustration we’ve heard from many teams using native Jira Software forms.

With Smart Forms for Jira, we specifically work with this limitation. All forms created with Smart Forms are automatically available across all Jira projects. You don’t need to recreate anything — just select the form from your library and add wherever you need.

Additionally:

• When you clone or move an issue, the forms attached to it move too, no matter draft or submitted.

• You can add multiple forms to a single issue, including public ones.

• And when a form is submitted, you can update issue fields, trigger status transitions, or even create new work items — all without rebuilding logic per project.