Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-986

Enable non-admin support for jira:workflowPostFunction in Forge

XMLWordPrintable

    • 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.

      We are currently facing a critical issue with the jira:workflowPostFunction module in Forge that is hindering our migration efforts from Connect to Forge.
      In Connect, non-admin users with the EDIT_WORKFLOWS permission can seamlessly edit Post-Functions in Jira workflows, even if the workflow is not shared with multiple projects. However, in Forge, non-admin users are unable to invoke remotes from the Custom UI. This limitation is preventing our Forge app from connecting to our backend services, effectively breaking functionality for non-admin users.

      As a developer, we would like to request an enhancement to the Forge platform that allows the jira:workflowPostFunction module to support remote invocations from the Custom UI for non-admin users, provided they have the necessary permissions (e.g., EDIT_WORKFLOWS) and the workflow is not shared across multiple projects.

      Refer https://ecosystem.atlassian.net/browse/FRGE-1865 for reproducible steps.

      Workaround

      Provide App Admin access to user as shown below:

              Unassigned Unassigned
              54bf2707b706 Deepak Pandey
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: