Open issues

Order by Priority
  1. Suggestion
    ECO-951Show more information on 'Atlassian' connected third-party account access
  2. Suggestion
    ECO-244As a site or org admin, I want to be able to use the apps when logged in as another user
  3. Suggestion
    ECO-946Page Content Reverts in Edit Mode After Macro Migration
  4. Suggestion
    ECO-945UI Kit adminPage subpages do not re-render on navigation
  5. Suggestion
    ECO-470Usage statistics for third party apps
  6. Suggestion
    ECO-939We need to retrieve the merge actor for the PR but can only retrieve the PR author. Information isn't available in the event, context, PR object, or any other accessible object.
  7. Suggestion
    ECO-838asUser API requests for JSM portal only (customer account) users
  8. Suggestion
    ECO-897Forge Custom Fields on Bulk Edit view
  9. Suggestion
    ECO-916Increase Resource Limit per manifest.yml
  10. Suggestion
    ECO-812Highlighting of "defined" terms
  11. Suggestion
    ECO-938Allow Customization of App Uninstallation Warning Message
  12. Suggestion
    ECO-880Open a modal dialog directly from a byline module in Confluence
  13. Suggestion
    ECO-918Support for Programmatic Refresh of Byline in Forge Apps
  14. Suggestion
    ECO-919Support for Wider or Configurable Byline Dialog Widths in Forge (Custom UI)
  15. Suggestion
    ECO-920Support for Non-Discoverable or Hidden Global Pages in Forge
  16. Suggestion
    ECO-917Support for Hidden or Non-Discoverable Macros in Forge
  17. Suggestion
    ECO-900As a Forge developer, I would like to emit cross-app events.
  18. Suggestion
    ECO-935As a Forge developer, I would like to trigger updates in customer sites without publishing a major version
  19. Suggestion
    ECO-934Add and identifier in the webhook to distinguish manual deletion from downstream project deletion and the order of events
  20. Suggestion
    ECO-930Incremental migration of Connect webItems to Forge not possible due to navigation limitations
  21. Suggestion
    ECO-776CreateIssueModal to be supported by edit/view custom field rendering module
  22. Suggestion
    ECO-875Support for (mTLS) Authentication in Jira Forge Apps for Web Triggers and External API Calls
  23. Suggestion
    ECO-765Requesting data from Atlassian systems still requires egress settings
  24. Suggestion
    ECO-928User email API returns 404 when the user is unlicensed or does not have the required roles to the product.
  25. Suggestion
    ECO-95Client Credential Grant Flow for OAuth 2.0 for external OAuth2 apps
  26. Suggestion
    ECO-74Integrate organizations Rest API into Forge
  27. Suggestion
    ECO-822Allow Forge Apps to Access Restricted Confluence Pages When Granted Admin-Level Scopes
  28. Suggestion
    ECO-926Support the usage of both invoke() and invokeRemote() in a forge module
  29. Suggestion
    ECO-896Provide support for UiModification on ViewIssueModal in Forge
  30. Suggestion
    ECO-223Bitbucket forge app should be able to make a Jira request
  31. Suggestion
    ECO-924Add ability to disable scheduled triggers for unlicensed apps
  32. Suggestion
    ECO-923Custom UI for Search on Custom Fields in Jira Cloud
  33. Suggestion
    ECO-922Enable direct access to Forge KVS Store via @forge/bridge
  34. Suggestion
    ECO-763Skip sending product events for unlicensed installations
  35. Suggestion
    ECO-595Please provide a feature to delete entities in the Forge Developement environment
  36. Suggestion
    ECO-915Allow Forge apps to add an icon in module confluence:contentAction
  37. Suggestion
    ECO-914Forge to support displaying external pages that requires user authentication through browser/Frontend
  38. Suggestion
    ECO-911Unable to Add Validator Rule to Workflow via REST API
  39. Suggestion
    ECO-901The "confluence:pageBanner" is not supported on the content types Smartlink, Database and Whiteboard
  40. Suggestion
    ECO-907Add Support for Scoped API Tokens in Forge CLI
  41. Suggestion
    ECO-905As an app vendor, I would like Forge to introduce more seamless extension points to provide consent.
  42. Suggestion
    ECO-903Forge specific app_key value for Bitbucket endpoints
  43. Suggestion
    ECO-904Provide API support to retrieve email addresses of workspace users in Bitbucket Cloud
  44. Suggestion
    ECO-902Add support for AbortSignal in requestJira
  45. Suggestion
    ECO-899Ability to access additional response headers when using requestJira
  46. Suggestion
    ECO-578Provide customers with the option to subscribe and receive emails from the Development Platform Changelog page
  47. Suggestion
    ECO-802The Managed App in the new location under Administration Connect Apps is lacking information
  48. Suggestion
    ECO-898Enable programmatic bulk installation of paid apps via the GraphQL API.
  49. Suggestion
    ECO-889No concept of a current board in Forge
  50. Suggestion
    ECO-884The "Web-Panel: atl.general" is not visible on the content types Smartlink, Database and Whiteboard
Refresh results
18 of 496
Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-935

As a Forge developer, I would like to trigger updates in customer sites without publishing a major version

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

      Apps that serve schemas or data provided by the developer of the app currently have to trigger Major version upgrades in customer sites to receive lifecycle events.

      As a developer that will update the data that is stored in the app, it would be useful to have a mechanism that allows us to trigger update events without triggering a major upgrade.

            No work has yet been logged on this issue.

              Unassigned Unassigned
              resteves Rodrigo Heinzen
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: