Tomas Bjerre

This just make me more confused. If you are using *HTTP Request Post-Receive Hook* why do you report the issue in this plugin?

The issue template, [here](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/blob/master/ISSUE_TEMPLATE), contains: > * Your configuration: > * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings > * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings/buttons > * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings/notifications Can you provide that? A guess could be that the `regexp filter`...

Ok. A support ticket on Atlassian is probably the only option then.

Yes should be compatible.

Available here: https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/releases See also https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/issues/313

There is a `${PULL_REQUEST_COMMENT_ID}` did you try that?

I made a quick test and it works for me. I can create notifications and buttons.

I made [a small docker-compose](https://github.com/tomasbjerre/jenkinsbitbucket) to ease fiddle with this. I found another issue. That if you create a button as a project admin, and dont select visibilty, the button...

You can find it in the rest-endpoints: * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings/buttons * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings/notifications

You need to be logged on with a user that has credentials to view the problematic repository. Den mån 11 feb. 2019 09:38mbrennerby skrev: > The URL is shown in...