How are ProForma customers migrating their JSW forms to the cloud without Jira Service Management?

[Rob Horan]

My understanding is that ProForma was integrated exclusively into Jira Service Management (JSM) Cloud, and the forms now available in Jira Cloud outside of JSM are a separate feature, not a direct continuation of ProForma. As such, ProForma content cannot be migrated directly.

How are ProForma customers migrating to the cloud without JSM?

I have searched the community and read through the page below, but so far I haven't found a clear, definitive migration path.

https://community.atlassian.com/t5/Jira-articles/A-new-way-to-manage-intake-in-Jira/ba-p/2856309

Do the forms have to be manually recreated one by one? 

[Olha Yevdokymova_SaaSJet]

Hi @Rob Horan 

Unfortunately, ProForma content cannot be directly migrated to Jira Cloud without JSM, leaving many customers in need of alternatives for their non-JSM projects.

To address this challenge, I recommend exploring Smart Forms for Jira add-on developed by my team. This app offers a robust solution for managing forms across Jira projects, including those outside of Jira. Here's how Smart Forms can help:

Why Smart Forms for Jira?

1. Cross-Project Compatibility
   Smart Forms works seamlessly in Jira Software, Jira Product Discovery, Jira Work Management, and JSM, ensuring you can manage forms in any Jira project type.

2. Advanced Form Features

   • Drag-and-drop form builder for easy customization.
   • Pre-fill options to populate form fields with Jira issue data.
   • Conditional logic for dynamic, user-responsive forms.

3. Streamlined Migration
   While forms need to be rebuilt, Smart Forms simplifies the process with its intuitive form builder and customizable templates. Forms can be build in secods with AI form builder

4. Seamless Integration

   • Attach forms directly to Jira issues.
   • Auto-attach forms based on project and issue type
   • Use forms to create new Jira issues automatically, mapping responses to fields like Summary, Description, and custom fields.

5. External Sharing
   Share forms via public links or embed them on websites or Confluence pages, making it easier to collect input from non-Jira users.

6. Real-Time Notifications
   Notify teams or users upon form submission, keeping workflows on track.

How to Get Started

1. Recreate Forms Efficiently: Use Smart Forms’ AI builder and intuitive builder to quickly recreate your ProForma forms with minimal effort.
2. Map Fields: Configure field mapping to ensure responses populate Jira issue fields automatically.
3. Share Forms: Embed forms in Confluence or share via links to continue collecting responses externally.
4. Automate Workflows: Leverage Jira Automation and Smart Forms to create efficient workflows tailored to your needs.

[Walter Buggenhout]

Hi @Rob Horan,

The short answer is: they aren't.

Forms in Jira (so, without JSM) are a brand new feature. As mentioned in the community article you shared:

We have no current plans to merge with the forms capability available in Jira Service Management and there will be no changes to any site which currently has these enabled for their Jira projects.

These Jira forms are much mure limited in capabilities than the ProForma forms Atlassian acquired some years ago and integrated into JSM only. As the article also mentions:

In addition to these, we will also be introducing conditional logic in the coming months. This will enable specific questions to be displayed or hidden, based on the answer selected in previous questions. Conditional logic will be available for priority, single, multi select, checkbox and radio custom fields.

As you seem to be a seasoned user of ProForma, I assume you are very much aware that the DC App goes a lot further than that, as do the forms in JSM. It is better to consider Jira forms as a much improved alternative to the OnPrem issue collector, rather than a downscaled version of ProForma.

So, unfortunately, there is no way to reproduce ProForma capabilities in Jira today and I do not expect the new Forms builder to quickly change that. As I coincidentally explained in a similar question that came in this week, I am afraid migrating to cloud will force you to reconsider your approach in Jira projects. While this may be a step back in form design, the cloud platform - luckily - has a lot of new capabilities that are not (and will never be) available on DC.

Hope this helps!

[Rob Horan]

Thanks - would you consider this a blocker to cloud migration for ProForma users then?