Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-17956

Azure DevOps integration and build status notifications

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 currently have our repositories in BitBucket and CI/CD pipelines in Azure DevOps (they are .NET projects).

      When a commit triggers a build in the CI via webhook, the build status is reported back to BitBucket correctly.

      Currently Azure DevOps has a feature that notification on build status can only be sent to "Team Members" which are Azure DevOps users and not BitBucket users. This means that it's not possible to configure build notification at Azure Devop's side for the user who did the push.

      For more information, please see the issue I opened at Azure Devops' side: https://developercommunity.visualstudio.com/content/problem/421119/notification-not-sent-for-triggered-ci-builds-from.html(Link URL)

      I propose a feature for webhooks that would allow notification sent to the user who pushed the code.

            [BCLOUD-17956] Azure DevOps integration and build status notifications

            Matthew Hunter made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels Original: migrated New: migrated timeout-suggestion-bulk-close202108

            Matthew Hunter added a comment -
            Atlassian Update - August 2, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - August 2, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3543258 ] New: JAC Suggestion Workflow 3 [ 3589363 ]
            Geoff created issue -

              Unassigned Unassigned
              ba9721c83d5b Juho Vainio
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: