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

Extend Forge Bitbucket events to contain project/repo keys/names

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.

      https://developer.atlassian.com/platform/forge/events-reference/bitbucket/

      Currently Bitbucket events generated by Forge contain only UUIDs for the workspace/project/repository. Typically these UUIDs are not well known - indeed the UUIDs are not even used widely in the Bitbucket REST API. Therefore consumers of the Forge events must translate the UUIDs to names/slugs. Which is a hassle.

      The Forge events for Jira contain the human-readable, well-known issue Key as well as the issue ID. Similarly, Forge events for Confluence contain the human-readable space Key, as well as the space ID.

      Can you please enhance the Forge Bitbucket events to also contain the human-readable names/keys? This will increase consistency, and make it easier for consumers of these events.

            [ECO-655] Extend Forge Bitbucket events to contain project/repo keys/names

            There are no comments yet on this issue.

              Unassigned Unassigned
              d49254792d3c jeremy.tangney
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: