Reminder - Changes coming into effect in Forms for Jira Service Managements

JSM Development JSM Cloud
, , ,
1

Hello Atlassian Developer Community,

As announced in our previous post in June 2024, we’ve now successfully completed the migration of Forms (previously ProForma) data from Jira Entity Properties. This will now enable us to build new functionality and increase performance and reliability of Forms.

Starting May 1 2025, we’ll begin removing access to historical Forms data accessible via Issue properties routes and Project properties routes in order for us to complete post-migration work.

You will still have full access to your Forms data though the Forms REST API.

We will also continue support for those currently using Jira Issue entity property smart values to access Forms data in Automation. We do however encourage you to consider moving any Automation to our new Forms smart values to better support your use-cases.

Thanks,

Mariia Zamorkina
Principal Engineer, Jira Service Management

1 Like
2

Great! We don’t need to change the existing JSM automation rules.

3

So true! Making sure that you don’t need to change any Automation rules that rely on {{issue.properties."proforma.forms.*"}} Smart Values was the main reason to we delayed access cut off. We definitely don’t want to force everyone to reconfigure every single rule. Unless you see it as an opportunity to try new Forms Smart Values :wink:

However, beware that if your configured something very custom, e.g. uses Issue properties routes and Project properties routes with Generic Automation Web action that needs to be moved to Forms Public API or Forms Smart Values, based on your preferences and use cases.