Add a Form using Automation and API

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 "Form Fields: Add additional forms based on previous fields filling", this article is meant to help users who want to use the new experimental features of the Forms API to automatically add a form in a ticket.


Workaround steps:

  • Create an Automation rule:
    • First, it will be needed to create an API token for the Web Request process. The Web Request needs your credentials and an API token encoded with base64.  For more information about this procedure, please refer to the documentation below:
      -    - Automation for Jira - Send web request using Jira REST API

    • We need to use the new API functionality of "Add form" in a Post web request. For example:
      • To add a form when an issue is transitioning to Escalated status:

        - The web method will be a POST:

        POST /jira/forms/cloud/{cloudId}/issue/{issueIdOrKey}/form

        - 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> You will get the Cloud id in the URL (e.g.:<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 {{}} or {{issue.key}}

        - It will be necessary to add the "main formId" of the desired form that you want to add. The "main formId" will be in the universally unique identifier "uuid" format. To get it you can use the Forms properties structure below:

        Screenshot 2023-06-09 at 18.29.13.png

        - The automation rule will be as shown in the screenshot below:Screenshot 2023-06-09 at 18.33.21.png

 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:



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events