From b8fbfa325b8624a3fc9f4576d70ec4439c42360b Mon Sep 17 00:00:00 2001 From: Tomas Bjerre Date: Sun, 13 Aug 2017 19:15:39 +0200 Subject: [PATCH] doc --- CHANGELOG.md | 4 ++++ ISSUE_TEMPLATE | 9 ++++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b5d93163..b276b6ba 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,10 @@ Changelog of Pull Request Notifier for Bitbucket. ## Unreleased ### No issue + Avoid race condition on save in GUI + + [776585222c0a31e](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/776585222c0a31e) Tomas Bjerre *2017-08-13 17:13:50* + doc [9b7e1818eac83aa](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/9b7e1818eac83aa) Tomas Bjerre *2017-08-13 16:41:06* diff --git a/ISSUE_TEMPLATE b/ISSUE_TEMPLATE index 70848434..530c6566 100644 --- a/ISSUE_TEMPLATE +++ b/ISSUE_TEMPLATE @@ -4,7 +4,6 @@ If things don't work as you expect, perhaps you should file an issue. But first, * Bitbucket Server version used. * Stack traces in Bitbucket Server log file. * Any browser console log messages, you can find it in Developer Tools in Chome by pressing F12. - * Screenshot of plugin configuration in your issue. Or the actual persisted settings: * Your configuration: * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings * http://localhost:7990/bitbucket/rest/prnfb-admin/1.0/settings/buttons @@ -12,3 +11,11 @@ If things don't work as you expect, perhaps you should file an issue. But first, * If the system you are trying to notify does not seem to get notified: * Check that the triggered URL looks as expected. You can do that by invoking https://requestb.in/ and inspect its results. * Try to SSH to the Bitbucket Server machine and run same URL with Curl to make sure it's not a firewall issue. + +If you do not have access to the server log files, one idea is to: + + * Also trigger on button pressed, and add a button + * Open a PR + * Open Chrome developer tools, F12 + * Press the button in the PR + * Check the response in the network tab in Chrome. See if it contains something interesting