Deprecation Notice: Removing access to Forms data using Jira entity properties API
To access forms properties after the deprecation, it will be necessary to use the new feature for Forms smart-values:
Alternatively, you can access these properties via the Jira Forms REST API.
The ability to access Forms data using the Jira entity properties API has been deprecated. This feature will be removed in future versions.
Work has already started on the new Forms API functionality and we now have some experimental APIs available for use. So now Marketplace Partners can already integrate forms into their products.
For more information, please refer to the features below:
As an extra option of workaround to the feature request "Forms Automation: In ProForma for Jira Cloud, allow copying forms between Issues with Automation", this article is meant to help users who want to use the new experimental features of the Forms API to automatically copy a form between tickets.
Copy a form on an issue status transition to a linked issue:
- The web method will be a POST:
POST https://api.atlassian.com/jira/forms/cloud/{cloudId}/issue/{sourceIssueIdOrKey}/form/copy/{targetIssueIdOrKey}
- The cloudId will be your Cloud ID and not your Org ID. The easy way to get the cloud id is to go to https://<instance>.atlassian.net/admin/jira-service-desk/portal-only-customers. You will get the Cloud id in the URL (e.g.: https://admin.atlassian.com/s/<cloud_id>/jira-service-desk/portal-only-customers)
- The issue ID or issue Key that you are using. To add the issueId or issueKey dynamically, you can use the smart value {{issue.id}} or {{issue.key}}
- The formId will be in the universally unique identifier "uuid" format. To get it you can use the Forms properties structure below:
https://<yourCloudURL>.atlassian.net/rest/api/2/issue/<issueId>/properties/proforma.forms
- To add the formId dynamically, you can use the smart value below:
{{issue.properties."proforma.forms".forms.uuid}}
- The targetIssueIdOrKey will be the issue that you want to copy. The icing on the cake here is to use the smart value below to get the ID of the linked issue:
{{issue.issuelinks.inwardIssue.key}}
- The automation rule will be as shown in the screenshot below:
Note: To call experimental methods the "
X-ExperimentalApi" and "opt-in"
header must be provided on the web request headers.
This workaround will work as shown in the screen recording below:
For different projects, the workaround will be the same, but with just a few more details:
This workaround will work as shown in the screen recording below:
Bruno Altenhofen
Atlassian Engineer - The guy from Proforma(Jira Forms)
e-Core
Krakow - Poland
1 accepted answer
12 comments