bitbucket does not send emails to [e-mail]

[Roland Haas]

Trac used to sent emails to [e-mail] but the current bitbucket tracker no longer does so.

Users have to either "watch" the repository or (better) we need to add a http hook to send the emails once more: https://bitbucket.org/einsteintoolkit/tickets/admin/addon/admin/bitbucket-webhooks/bb-webhooks-repo-admin

[Roland Haas]

Correction. This facility moved and is now found here: https://bitbucket.org/einsteintoolkit/tickets/admin/issues/mailing-list

[Roland Haas]

This does not seem to be quite sufficient.

1. it does not seem to work right now (at least I am not seeing any emails showing up for #2226
2. it only sends emails when issues are created, not when they are updated (see https://confluence.atlassian.com/bitbucket/setting-email-preferences-for-an-issue-tracker-223216507.html)

[Roland Haas]

I will have a proof-of-concept ready soon.

[Roland Haas]

A simple hook has been set up to send trac-like emails to [e-mail] (this being the only(?) address the server lets me send emails to) so that not everyone is spammed by testing emails.

The script is in hooks/issue_changed.php of the ET www repo.

This can be made to work on a local machine for testing by sending emails to just $USER@localhost, setting up a hook in private repository and adjusting the hook UUID used for authentication in the script.

[Roland Haas]

Testing email sender settings.

[Roland Haas]

Emails are now being sent about tickets being created, commented on and their status being updated.

There is no hook in place yet that would send comments from pull requests to [e-mail] yet.

[Roland Haas]

Our current script will be affected by https://developer.atlassian.com/cloud/bitbucket/bbc-gdpr-api-migration-guide/ in particular the change in visibility of the assignee user name on ticket changes.

[Roland Haas]

Check back in May to see if indeed we need to change anything or if the assignee change only affects actual API calls and not data being sent to webhooks.