Open issues

Order by Priority
  1. Suggestion
    ECO-984Forge: Missing parent Field in avi:jira:deleted:issue Event Payload
  2. Suggestion
    ECO-982Add Native Binary (BLOB) Support in Forge SQL SDK
  3. Suggestion
    ECO-981Allow a Forge JQL function fragment from a custom JQL function to invoke another custom JQL function
  4. Suggestion
    ECO-980Allow a Forge JQL function fragment from a custom JQL function to invoke another custom JQL function
  5. Suggestion
    ECO-244As a site or org admin, I want to be able to use the apps when logged in as another user
  6. Suggestion
    ECO-965Forge Storage should be part of the Atlassian-provided Backup & Restore capabilities
  7. Suggestion
    ECO-472Lower pop-up prompt when including Jira tickets in a Confluence Cloud page
  8. Suggestion
    ECO-900As a Forge developer, I would like to emit cross-app events.
  9. Suggestion
    ECO-470Usage statistics for third party apps
  10. Suggestion
    ECO-85It should be documented how the connect app user and groups work and how changing default product access groups can break apps
  11. Suggestion
    ECO-963Granular Permission Management for Connect Users Across Atlassian Products
  12. Suggestion
    ECO-978Support for Underlined Text in UI Kit Text Component
  13. Suggestion
    ECO-973Adding ADS Form Component to UI Kit
  14. Suggestion
    ECO-975JSM Assets API to be integrated natively on Forge
  15. Suggestion
    ECO-974Unable to use roaring NPM package in Forge runtime
  16. Suggestion
    ECO-972Unreliable Keyboard Events in jira:command Modal
  17. Suggestion
    ECO-971Allow resource for thumbnail property in Jira dashboard gadget
  18. Suggestion
    ECO-957Forge workflow validator function does not receive configuration in payload during Jira issue transitions
  19. Suggestion
    ECO-967Rendering of other macros or images within custom tabs
  20. Suggestion
    ECO-966Add Forge Modules for the Atlassian Teams pages
  21. Suggestion
    ECO-315App Usage for Jira Cloud
  22. Suggestion
    ECO-964Allow Alert Rules creation for Staging environment
  23. Suggestion
    ECO-961Forge App Does Not Receive Page-View or Page-Updated Events for Restricted Content
  24. Suggestion
    ECO-223Bitbucket forge app should be able to make a Jira request
  25. Suggestion
    ECO-466Ability to export the list of Connected apps and provide information about authentication method used by apps.
  26. Suggestion
    ECO-953Integrate DLP REST API into Forge
  27. Suggestion
    ECO-951Show more information on 'Atlassian' connected third-party account access
  28. Suggestion
    ECO-945UI Kit adminPage subpages do not re-render on navigation
  29. 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.
  30. Suggestion
    ECO-838asUser API requests for JSM portal only (customer account) users
  31. Suggestion
    ECO-897Forge Custom Fields on Bulk Edit view
  32. Suggestion
    ECO-916Increase Resource Limit per manifest.yml
  33. Suggestion
    ECO-812Highlighting of "defined" terms
  34. Suggestion
    ECO-938Allow Customization of App Uninstallation Warning Message
  35. Suggestion
    ECO-880Open a modal dialog directly from a byline module in Confluence
  36. Suggestion
    ECO-918Support for Programmatic Refresh of Byline in Forge Apps
  37. Suggestion
    ECO-919Support for Wider or Configurable Byline Dialog Widths in Forge (Custom UI)
  38. Suggestion
    ECO-920Support for Non-Discoverable or Hidden Global Pages in Forge
  39. Suggestion
    ECO-917Support for Hidden or Non-Discoverable Macros in Forge
  40. Suggestion
    ECO-935As a Forge developer, I would like to trigger updates in customer sites without publishing a major version
  41. Suggestion
    ECO-934Add and identifier in the webhook to distinguish manual deletion from downstream project deletion and the order of events
  42. Suggestion
    ECO-930Incremental migration of Connect webItems to Forge not possible due to navigation limitations
  43. Suggestion
    ECO-776CreateIssueModal to be supported by edit/view custom field rendering module
  44. Suggestion
    ECO-875Support for (mTLS) Authentication in Jira Forge Apps for Web Triggers and External API Calls
  45. Suggestion
    ECO-765Requesting data from Atlassian systems still requires egress settings
  46. Suggestion
    ECO-928User email API returns 404 when the user is unlicensed or does not have the required roles to the product.
  47. Suggestion
    ECO-95Client Credential Grant Flow for OAuth 2.0 for external OAuth2 apps
  48. Suggestion
    ECO-74Integrate organizations Rest API into Forge
  49. Suggestion
    ECO-822Allow Forge Apps to Access Restricted Confluence Pages When Granted Admin-Level Scopes
  50. Suggestion
    ECO-926Support the usage of both invoke() and invokeRemote() in a forge module
Refresh results
1 of 512
Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-984

Forge: Missing parent Field in avi:jira:deleted:issue Event Payload

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

      Parent field which is present in jira:issue_deleted webhook event for connect app, is not present in the corresponding avi:jira:deleted:issue for forge. 

       

      Request

      Please add Parent field in the webhook event, similar to how it was for connect.

            There are no comments yet on this issue.

              Unassigned Unassigned
              de18e5af647f Faisal
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: