Open issues

Order by Priority
  1. Suggestion
    FORMDC-805Automation form does not works when fire other event than Generic Event
  2. Suggestion
    FORMDC-842Grant the Project Administrator permission to have access to Proforma Forms by default
  3. Suggestion
    FORMDC-840Proforma does not sync the default value of a custom field from a required question, if that question is hidden by a section
  4. Suggestion
    FORMDC-29Allow the ability to export/import Proforma forms data
  5. Suggestion
    FORMDC-808Provide support for cascade select list type of custom field in ProForma forms
  6. Suggestion
    FORMDC-518Ability to show ProForma Form before Customer Request fields
  7. Suggestion
    FORMDC-813ProForma Fix Version/s linked Field shows Archived versions
  8. Suggestion
    FORMDC-841Insight fields support in ProForma forms
  9. Suggestion
    FORMDC-826Provide the ability to restrict one Form to an issue
  10. Suggestion
    FORMDC-55ProForma limitations with Configuration Manager for Jira
  11. Suggestion
    FORMDC-2Ability to use choice questions values in automations
  12. Suggestion
    FORMDC-839Update the Proforma documentation "Forms and requests" as it is unclear
  13. Suggestion
    FORMDC-817Need audit logs for Proforma when performing any actions
  14. Suggestion
    FORMDC-797Implement audit history
  15. Suggestion
    FORMDC-526Forms: Allow multiple forms for a single request type in the customer portal
  16. Suggestion
    FORMDC-837Include Forms when cloning an issue
  17. Suggestion
    FORMDC-827Form Conditions: More possibilities with conditions
  18. Suggestion
    FORMDC-836Review "Restore Permissions" section on Proforma Permissions Page
  19. Suggestion
    FORMDC-835Add support for Proforma Automation to submit a form when the issue transitions to a specific status
  20. Suggestion
    FORMDC-834Allow image upload on Forms
  21. Suggestion
    FORMDC-27Proper proforma/forms integration with Insight fields
  22. Suggestion
    FORMDC-43Add option to specify the Attachment field as part of the Proforma Questions
  23. Suggestion
    FORMDC-821Anonymous users on the portal
  24. Suggestion
    FORMDC-833ProForma Unsaved Changes Warning
  25. Suggestion
    FORMDC-15Dynamic validation - Prevent submission of Form depending on form responses
  26. Suggestion
    FORMDC-74Form Field: Paragraph - support rich text editing
  27. Suggestion
    FORMDC-42Form Field: Paragraph - support multiline and rich default response
  28. Suggestion
    FORMDC-40Epic Link field option missing under Jira Linked Field list in ProForma
  29. Suggestion
    FORMDC-794Ability to integration with Elements Connect
  30. Suggestion
    FORMDC-831Ability to display the Proforma forms based on a custom field value selected by the user
  31. Suggestion
    FORMDC-829Ability to restrict the Download formats of the Proforma forms in issue view screen
  32. Suggestion
    FORMDC-828Proforma forms in the portal should have consistent spacing between fields
  33. Suggestion
    FORMDC-825Increase the size limit of the Forms that include custom scripts from default 32KB
  34. Suggestion
    FORMDC-822Ability to validate JSON responses obtained from Data Connections in Forms
  35. Suggestion
    FORMDC-819Provide the ability to Restrict Forms based on "Issue Type"
  36. Suggestion
    FORMDC-815Allow a single "live" form to apply to multiple projects
  37. Suggestion
    FORMDC-814Option to include Issue Attributes in ProForma export
  38. Suggestion
    FORMDC-811Add vars for REST calls in Connections
  39. Suggestion
    FORMDC-810Add vars for REST calls in Connections
  40. Suggestion
    FORMDC-809Add the ability to process REST results for Connections
  41. Suggestion
    FORMDC-807Required Radio Button doesn't enforce Other test to be provided
  42. Suggestion
    FORMDC-801Provide a REST API to get the Forms layout with options of data connections
  43. Suggestion
    FORMDC-799Display in UI any error related to field update
  44. Suggestion
    FORMDC-798Update the question min/max chars limits when mapping to a field that is limited
  45. Suggestion
    FORMDC-796Improve the Proforma field linking functionality to set the Jira field at issue creation
  46. Suggestion
    FORMDC-793Ability to attach forms in automation for Jira
  47. Suggestion
    FORMDC-790Set Proforma to use jira.date.time.picker setting
  48. Suggestion
    FORMDC-788Provide PDF/A Support in ProForma
  49. Suggestion
    FORMDC-786Ability to ProForma user picker field linked to a Jira user picker field reflect any constraints (filtering to specific groups) that exist on the Jira field
  50. Suggestion
    FORMDC-784Ability to change image size
Refresh results
1 of 125
Uploaded image for project: 'Proforma Server & Data Centre'
  1. Proforma Server & Data Centre
  2. FORMDC-805

Automation form does not works when fire other event than Generic Event

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Automation
    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Add form automation to the following:
      2. Navigate to the Done workflow transition.
      3. Modify the Fire Event post-function from "Generic Event" to "Issue Resolved" event: 
        Fire a Issue Resolved event that can be processed by the listeners.
      4. Publish the workflow.
      5. Create a new issue and change the status to "Done" and the new form is not added.

      A video recording to demo the issue: Screen Recording 2024-09-19 at 1.30.16 PM.mov

      Expected Results

      Proforma automation creation form should be listening to any events or not depending on specific event to trigger the form.

      Actual Results

      Proforma automation creation form only listen to Generic Event.

      Workaround

      • Change the Fire Event to Generic Event in the workflow post-function.
      • If you want to fire other custom Event, you may want to add a new Fire Event post-function for the custom event.

        1. image-2024-08-16-09-37-36-841.png
          image-2024-08-16-09-37-36-841.png
          45 kB
        2. Screen Recording 2024-09-19 at 1.30.16 PM.mov
          36.59 MB

          Form Name

            Tanu Garg added a comment -

            This is a feature request. As per our documentation ProForma currently only support generic events.
            [ProForma automation | Atlassian Support | Atlassian Documentation|https://confluence.atlassian.com/proforma/proforma-automation-1087521265.html]

            Tanu Garg added a comment - This is a feature request . As per our documentation ProForma currently only support generic events. [ProForma automation | Atlassian Support | Atlassian Documentation|https://confluence.atlassian.com/proforma/proforma-automation-1087521265.html]

              Unassigned Unassigned
              ckimloong John Chin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: