Disconnect between deprecated Services and new Webhook leaving some of us high and dry

Issue #14030 resolved
Ryan Hinton
created an issue

My older repos have a service link in the settings to allow us to set up Pivotal Tracker with a Token and everything comes to life for our automation. However, there is a disconnect as to how this can be achieved using webhooks. All of the details are hidden in a service that we don't know how to replicate in a web hook for newer repos that no longer have the services link in the settings. What is the solution for us to be able to bridge the gap for Pivotal Tracker between the deprecated services and the new webhooks so that all of us can continue to use our automation with Pivotal Tracker with newer repos, please?

Comments (14)

  1. Sandeep Srinivasa

    +1 i have the same issue with email notifications. I had emails sent to a review group email address on commit, pull or issue. now I need to implement this myself and I have no idea how to.

    This was a basic feature that was removed and guess what - the older repositories still have it. This is not nice.

  2. Alastair Wilkes

    Hi all,

    First off, I want to apologize for the way the services deprecation was originally handled.

    In hindsight, it would have been better to target the deprecation at the account level, not the repository level, which would allow customers already using integrations like these to keep using them on new repos (as we still support them on existing repos) but customers who weren't using them already wouldn't be able to create new ones.

    As a workaround for this, while the hooks page is hidden for new repos, it is still accessible via URL. That URL is

    https://bitbucket.org/<user>/<repo>/admin/hooks

    Hope that helps, and sorry for the inconvenience.

    Alastair

  3. Log in to comment