- ECO-928User email API returns 404 when the user is unlicensed or does not have the required roles to the product.
- ECO-95Client Credential Grant Flow for OAuth 2.0 for external OAuth2 apps
- ECO-900As a Forge developer, I would like to emit cross-app events.
- ECO-74Integrate organizations Rest API into Forge
- ECO-822Allow Forge Apps to Access Restricted Confluence Pages When Granted Admin-Level Scopes
- ECO-244As a site or org admin, I want to be able to use the apps when logged in as another user
- ECO-926Support the usage of both invoke() and invokeRemote() in a forge module
- ECO-896Provide support for UiModification on ViewIssueModal in Forge
- ECO-470Usage statistics for third party apps
- ECO-223Bitbucket forge app should be able to make a Jira request
- ECO-924Add ability to disable scheduled triggers for unlicensed apps
- ECO-923Custom UI for Search on Custom Fields in Jira Cloud
- ECO-922Enable direct access to Forge KVS Store via @forge/bridge
- ECO-763Skip sending product events for unlicensed installations
- ECO-916Increase Resource Limit per manifest.yml
- ECO-918Support for Programmatic Refresh of Byline in Forge Apps
- ECO-595Please provide a feature to delete entities in the Forge Developement environment
- ECO-920Support for Non-Discoverable or Hidden Global Pages in Forge
- ECO-915Allow Forge apps to add an icon in module confluence:contentAction
- ECO-919Support for Wider or Configurable Byline Dialog Widths in Forge (Custom UI)
- ECO-917Support for Hidden or Non-Discoverable Macros in Forge
- ECO-914Forge to support displaying external pages that requires user authentication through browser/Frontend
- ECO-911Unable to Add Validator Rule to Workflow via REST API
- ECO-901The "confluence:pageBanner" is not supported on the content types Smartlink, Database and Whiteboard
- ECO-907Add Support for Scoped API Tokens in Forge CLI
- ECO-484Manifest flag to automatically open the config sidebar
- ECO-905As an app vendor, I would like Forge to introduce more seamless extension points to provide consent.
- ECO-903Forge specific app_key value for Bitbucket endpoints
- ECO-904Provide API support to retrieve email addresses of workspace users in Bitbucket Cloud
- ECO-902Add support for AbortSignal in requestJira
- ECO-838asUser API requests for JSM portal only (customer account) users
- ECO-899Ability to access additional response headers when using requestJira
- ECO-578Provide customers with the option to subscribe and receive emails from the Development Platform Changelog page
- ECO-802The Managed App in the new location under Administration Connect Apps is lacking information
- ECO-898Enable programmatic bulk installation of paid apps via the GraphQL API.
- ECO-889No concept of a current board in Forge
- ECO-884The "Web-Panel: atl.general" is not visible on the content types Smartlink, Database and Whiteboard
- ECO-895Discrepancy in how @atlaskit/badge is rendered in the refreshed UI style between UI Kit and Custom UI
- ECO-283OAuth 2.0 with Proof Key for Code Exchange (PKCE)
- ECO-728Allow *.atl-paas.net domain for apps built with Forge UI Kit
- ECO-686Provide an option to implement Full-Screen Modal Dialog
- ECO-893Feature Request: Markdown Export for Editor Components
- ECO-892Allow users without "Edit Issue" permission to enable/disable jira:issuePanel module
- ECO-421Improve error messaging for permission related issue panel action
- ECO-891Add type validation in jira:entityProperty values
- ECO-866Support behaviors, live fields, custom validations in the 'Create Linked Work Item' screen
- ECO-883Add "Assets objects" fields to Jira add-ins for Outlook and Teams.
- ECO-882Better support for multiple modules with shared resources
- ECO-881Limit API tokens to specific sites
- ECO-880Open a modal dialog directly from a byline module in Confluence
1 of 480