pull-request-notifier-for-bitbucket

pull-request-notifier-for-bitbucket copied to clipboard

How to use BUTTON_FORM_DATA in as url param

[{"_id":"63843fce4b97542c9a3546db","body":"> I would need to use data from the `BUTTON_FORM_DATA` as url parameters. Is this possible?\r\n> I can add the entire form data like `https:\/\/someurl.com?data=${BUTTON_FORM_DATA}`, but I would need to access the fields. Something like `https:\/\/someurl.com?a=${BUTTON_FORM_DATA.a}&b=${BUTTON_FORM_DATA.b}`. Any hints?\r\n\r\n@jakob-grabner just checking in to see if you were ever able to figure out how to pass a specific variable within ${BUTTON_FORM_DATA}? also looking to do the same thing and can\u2019t find any documentation on this.\r\n","issue_id":1660325302363,"origin_id":844590520,"user_origin_id":6157895,"create_time":1621470892,"update_time":1621470892,"id":1669611470870,"updated_at":"2022-11-28T04:57:50.870000Z","created_at":"2022-11-28T04:57:50.870000Z"}]

I would need to use data from the `BUTTON_FORM_DATA` as url parameters. Is this possible? I can add the entire form data like `https://someurl.com?data=${BUTTON_FORM_DATA}`, but I would need to access...

jakob-grabner

Bitbucket 7.1.1 support --- Buttons doesn't appear

[{"_id":"63844f89bc25e83db00f3618","body":"Can confirm the problem. I think I've traced it down to this change in 7.0 Bitbucket release:\r\nhttps:\/\/developer.atlassian.com\/server\/bitbucket\/reference\/api-changelog\/#changes-related-to-the-new-pull-request-experience-\r\nSadly, I have no experience with plugin development. So maybe this pointer can help somebody open a PR.","issue_id":1660325302367,"origin_id":620490010,"user_origin_id":9142227,"create_time":1588066071,"update_time":1588066071,"id":1669615497438,"updated_at":"2022-11-28T06:04:57.438000Z","created_at":"2022-11-28T06:04:57.438000Z"},{"_id":"63844f89bc25e83db00f3619","body":"@tomasbjerre any help here ?","issue_id":1660325302367,"origin_id":631983653,"user_origin_id":29040669,"create_time":1590053153,"update_time":1590053183,"id":1669615497443,"updated_at":"2022-11-28T06:04:57.443000Z","created_at":"2022-11-28T06:04:57.443000Z"},{"_id":"63844f89bc25e83db00f361a","body":"See top of the readme in this repo.\n\nDen tors 21 maj 2020 11:26Kirill Kamaldinov <[email protected]>\nskrev:\n\n> @tomasbjerre <https:\/\/github.com\/tomasbjerre> any help here ?\n>\n> \u2014\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub\n> <https:\/\/github.com\/tomasbjerre\/pull-request-notifier-for-bitbucket\/issues\/366#issuecomment-631983653>,\n> or unsubscribe\n> <https:\/\/github.com\/notifications\/unsubscribe-auth\/AADLKEYIPWZXQEUXQYYMWT3RSTXS5ANCNFSM4MMK4KFQ>\n> .\n>\n","issue_id":1660325302367,"origin_id":631991744,"user_origin_id":439571,"create_time":1590054237,"update_time":1590054237,"id":1669615497446,"updated_at":"2022-11-28T06:04:57.445000Z","created_at":"2022-11-28T06:04:57.445000Z"},{"_id":"63844f89bc25e83db00f361b","body":"I can also confirm that this no longer works. Plugin version 4.1 and BitBucket Server 7.2.3.\r\n\r\nI wish to thank @tomasbjerre for making this plugin in the first place. It has served us well!. But it seems Atlassian keeps mixing things up. We'll have to redesign our CI solutions. Maybe ditch bitbucket alltogether.","issue_id":1660325302367,"origin_id":633872964,"user_origin_id":10220637,"create_time":1590480124,"update_time":1590480124,"id":1669615497450,"updated_at":"2022-11-28T06:04:57.449000Z","created_at":"2022-11-28T06:04:57.449000Z"},{"_id":"63844f89bc25e83db00f361c","body":"I appeared to run into this same issue, but on a combination of upgrades NOT involving Bitbucket 7.x:\r\n\r\n- PR Notifier 4.1 -> 5.0\r\n- Bitbucket DC 6.10.5 -> 6.10.8.\r\n\r\nHas anyone else seen similar behavior with similar combinations? Reverting to PR Notifier 4.1 did not have any effect. So, we no longer have ANY trigger build buttons, which was one of the best functionalities provided by PR Notifier.","issue_id":1660325302367,"origin_id":785376521,"user_origin_id":55840555,"create_time":1614199952,"update_time":1614199952,"id":1669615497454,"updated_at":"2022-11-28T06:04:57.454000Z","created_at":"2022-11-28T06:04:57.454000Z"},{"_id":"63844f89bc25e83db00f361e","body":"I am also facing this issue. In case of not going to fix this plugin, is there any equivalent alternative for Bitbucket 7?","issue_id":1660325302367,"origin_id":792757832,"user_origin_id":28559743,"create_time":1615210271,"update_time":1615210271,"id":1669615497458,"updated_at":"2022-11-28T06:04:57.457000Z","created_at":"2022-11-28T06:04:57.457000Z"},{"_id":"63844f89bc25e83db00f361f","body":"> Has anyone else seen similar behavior with similar combinations? Reverting to PR Notifier 4.1 did not have any effect. So, we no longer have ANY trigger build buttons, which was one of the best functionalities provided by PR Notifier.\r\n\r\nI have bitbucket server v6.10.8 and PR Notifier 4.1 and with that setup all is working fine. As you can see, we have the buttons \"Delegate Merge\" and \"Launch Jenkins Build\" in the PR right-side menu.\r\n\r\n\r\n\r\n\r\nBut if I do an upgrade of the PR Notifier from 4.1 to 5.0 (the latests release, without upgrading bitbucket), those buttons are not displayed anymore.\r\nAnd the same happened last week; after upgrading to Bitbucket 7.6 and PR Notifier 4.1; buttons were not there anymore.\r\n\r\n\r\nIs there any combination between PR Notifier and Bitbucket 7.X that works correctly?\r\n","issue_id":1660325302367,"origin_id":800149665,"user_origin_id":28559743,"create_time":1615891297,"update_time":1615891357,"id":1669615497461,"updated_at":"2022-11-28T06:04:57.461000Z","created_at":"2022-11-28T06:04:57.461000Z"}]

Can't see button anymore (after u[grade from 6.10 to 7.1.1) * Plugin version: LATEST - 4.1 * Bitbucket Server version: 7.1.1 [{"buttonFormList":[],"buttonFormListString":"[]","confirmation":"on","name":"BUILD","projectKey":"A00P","repositorySlug":"a00_repo_template_1","userLevel":"ADMIN","uuid":"a4049b47-538e-48f8-93a1-abc2a82eb2c6","confirmationText":"Are you sure?"},{"buttonFormList":[],"buttonFormListString":"[]","confirmation":"on","name":"Deploy to Production","projectKey":"GT","userLevel":"ADMIN","uuid":"d8b8384e-3c19-4d0b-88ce-6e5013a4db1a","confirmationText":"The changes of the pull...

ApresFiux

Pull Request Buttons are not working Post upgrade

[{"_id":"63844b99bc25e83db00f2e7a","body":"Can we get an update here?","issue_id":1660325302370,"origin_id":756157682,"user_origin_id":44606563,"create_time":1610030513,"update_time":1610030513,"id":1669614489617,"updated_at":"2022-11-28T05:48:09.617000Z","created_at":"2022-11-28T05:48:09.617000Z"},{"_id":"63844b99bc25e83db00f2e7b","body":"Check the changelog.","issue_id":1660325302370,"origin_id":756172688,"user_origin_id":439571,"create_time":1610032013,"update_time":1610032013,"id":1669614489621,"updated_at":"2022-11-28T05:48:09.621000Z","created_at":"2022-11-28T05:48:09.621000Z"},{"_id":"63844b99bc25e83db00f2e7c","body":"Could you please suggest us where we need check??","issue_id":1660325302370,"origin_id":756186109,"user_origin_id":44606563,"create_time":1610033303,"update_time":1610033303,"id":1669614489624,"updated_at":"2022-11-28T05:48:09.624000Z","created_at":"2022-11-28T05:48:09.624000Z"},{"_id":"63844b99bc25e83db00f2e7d","body":"We are awaiting for your response on this topic.","issue_id":1660325302370,"origin_id":762846312,"user_origin_id":44606563,"create_time":1611063723,"update_time":1611063723,"id":1669614489627,"updated_at":"2022-11-28T05:48:09.627000Z","created_at":"2022-11-28T05:48:09.627000Z"},{"_id":"63844b99bc25e83db00f2e7e","body":"Could you please provide us an update here\r\n","issue_id":1660325302370,"origin_id":796858884,"user_origin_id":44606563,"create_time":1615479649,"update_time":1615479649,"id":1669614489632,"updated_at":"2022-11-28T05:48:09.631000Z","created_at":"2022-11-28T05:48:09.631000Z"}]

Hello Team, Recently we have upgraded our Bitbucket from 6.10.4 to 7.6 LTS. Post upgrade we are facing an issue with custom buttons on pull request view. We are configuring...

gsep-support

Using filterString and filterRegexp

[{"_id":"63844cdb4b97542c9a355dc9","body":"Let the filter string be `${PULL_REQUEST_TO_BRANCH}` and the filter regexp be `master`.","issue_id":1660325302374,"origin_id":357689424,"user_origin_id":439571,"create_time":1516024548,"update_time":1516024548,"id":1669614811670,"updated_at":"2022-11-28T05:53:31.669000Z","created_at":"2022-11-28T05:53:31.669000Z"},{"_id":"63844cdb4b97542c9a355dca","body":"Awesome, thanks for the super-fast answer!","issue_id":1660325302374,"origin_id":357690333,"user_origin_id":4911961,"create_time":1516024774,"update_time":1516024774,"id":1669614811674,"updated_at":"2022-11-28T05:53:31.674000Z","created_at":"2022-11-28T05:53:31.674000Z"},{"_id":"63844cdb4b97542c9a355dcb","body":"Perhaps you need regexp to be `^master$`... there is a test case here: https:\/\/github.com\/tomasbjerre\/pull-request-notifier-for-bitbucket\/blob\/master\/src\/test\/java\/se\/bjurr\/prnfb\/listener\/PrnfbPullRequestEventListenerTest.java#L378","issue_id":1660325302374,"origin_id":357690344,"user_origin_id":439571,"create_time":1516024777,"update_time":1516024777,"id":1669614811676,"updated_at":"2022-11-28T05:53:31.676000Z","created_at":"2022-11-28T05:53:31.676000Z"},{"_id":"63844cdb4b97542c9a355dcd","body":"Hi,\r\nI have a similar question related to filter and regexp.\r\nI would like to have notification which is triggered when ${PULL_REQUEST_TO_BRANCH} = develop or master, and additionally, there should be the possibility to trigger the notification by pressing the button.\r\n\r\nI suppose it should be something like that:\r\n\r\nFilter string: ${PULL_REQUEST_TO_BRANCH}${BUTTON_TRIGGER_TITLE}\r\nFilter regexp: ^(develop|master)$|<button name>\r\n\r\nI tried different ways, but couldn't combine those two conditions.\r\n\r\nCould you please help with that?","issue_id":1660325302374,"origin_id":373337739,"user_origin_id":37402727,"create_time":1521111506,"update_time":1521111506,"id":1669614811683,"updated_at":"2022-11-28T05:53:31.682000Z","created_at":"2022-11-28T05:53:31.682000Z"},{"_id":"63844cdb4b97542c9a355dce","body":"Any button or a specific one?\r\n\r\nFilter string: `${PULL_REQUEST_TO_BRANCH}_${BUTTON_TRIGGER_TITLE}_`\r\nFilter regexp: `^(develop|master)_.+_$` or `^(develop|master)(?!__$)`\r\nIf it is a specific button, the filter regexp can be perhaps `^(develop|master)_That button name_$`","issue_id":1660325302374,"origin_id":373352366,"user_origin_id":439571,"create_time":1521115128,"update_time":1521115128,"id":1669614811685,"updated_at":"2022-11-28T05:53:31.685000Z","created_at":"2022-11-28T05:53:31.685000Z"},{"_id":"63844cdb4b97542c9a355dcf","body":"Thanks for quick answer.\r\nI would like to have the specific button for notification. Button name: build-pr\r\n\r\nAfter setting it:\r\n\r\nFilter string: ${PULL_REQUEST_TO_BRANCH}_${BUTTON_TRIGGER_TITLE}_\r\nFilter regexp: ^(develop|master)_build-pr_$\r\n\r\nthe button has appeared, but the build wasn't triggered automatically when I created PR.\r\n\r\n","issue_id":1660325302374,"origin_id":373361615,"user_origin_id":37402727,"create_time":1521117471,"update_time":1521117471,"id":1669614811688,"updated_at":"2022-11-28T05:53:31.687000Z","created_at":"2022-11-28T05:53:31.687000Z"},{"_id":"63844cdb4b97542c9a355dd0","body":"Ok. With filter string like `${PULL_REQUEST_TO_BRANCH}_${BUTTON_TRIGGER_TITLE}_` this should work `^(develop|master)(_build-pr_|__)$`","issue_id":1660325302374,"origin_id":373377337,"user_origin_id":439571,"create_time":1521120915,"update_time":1521120915,"id":1669614811690,"updated_at":"2022-11-28T05:53:31.689000Z","created_at":"2022-11-28T05:53:31.689000Z"},{"_id":"63844cdb4b97542c9a355dd1","body":"It works now.\r\nThanks a lot!\r\nThe button has appeared in the pr context menu, but I see some strange empty lines there:\r\n\r\n\r\nDo you know the reason?","issue_id":1660325302374,"origin_id":373441249,"user_origin_id":37402727,"create_time":1521131834,"update_time":1521131834,"id":1669614811693,"updated_at":"2022-11-28T05:53:31.692000Z","created_at":"2022-11-28T05:53:31.692000Z"},{"_id":"63844cdb4b97542c9a355dd2","body":"No not sure why that happens. You only have one button configured right?","issue_id":1660325302374,"origin_id":373442232,"user_origin_id":439571,"create_time":1521132008,"update_time":1521132008,"id":1669614811695,"updated_at":"2022-11-28T05:53:31.695000Z","created_at":"2022-11-28T05:53:31.695000Z"},{"_id":"63844cdb4b97542c9a355dd3","body":"Yes, only one, at least for this particular repository.","issue_id":1660325302374,"origin_id":373453403,"user_origin_id":37402727,"create_time":1521133945,"update_time":1521133945,"id":1669614811697,"updated_at":"2022-11-28T05:53:31.697000Z","created_at":"2022-11-28T05:53:31.697000Z"},{"_id":"63844cdb4b97542c9a355dd5","body":"Hi,\r\n\r\nI have similar issue, I would like to trigger Jenkins when ${PULL_REQUEST_REVIEWERS_UNAPPROVED_COUNT} = 0, and ${PULL_REQUEST_TO_BRANCH} = master or release\/*\r\n\r\nhow to set the filter?","issue_id":1660325302374,"origin_id":389081585,"user_origin_id":30495070,"create_time":1526371813,"update_time":1526371813,"id":1669614811701,"updated_at":"2022-11-28T05:53:31.700000Z","created_at":"2022-11-28T05:53:31.700000Z"},{"_id":"63844cdb4b97542c9a355dd6","body":"This should work:\r\n\r\nFilter: `${PULL_REQUEST_REVIEWERS_UNAPPROVED_COUNT} ${PULL_REQUEST_TO_BRANCH}`\r\n\r\nRegexp: `0 (master|release\/.*)`\r\n\r\nhttps:\/\/jex.im\/regulex\/#!flags=&re=0%20(master%7Crelease%2F.*)","issue_id":1660325302374,"origin_id":389082810,"user_origin_id":439571,"create_time":1526372088,"update_time":1526372088,"id":1669614811703,"updated_at":"2022-11-28T05:53:31.703000Z","created_at":"2022-11-28T05:53:31.703000Z"},{"_id":"63844cdb4b97542c9a355dd7","body":"Hi,\r\nThanks for the quick reply.\r\nI was faced with a new problem.How to fill Regexp with variables?","issue_id":1660325302374,"origin_id":391238659,"user_origin_id":30495070,"create_time":1527058008,"update_time":1527058008,"id":1669614811707,"updated_at":"2022-11-28T05:53:31.706000Z","created_at":"2022-11-28T05:53:31.706000Z"},{"_id":"63844cdb4b97542c9a355dd8","body":"The regexp field does not support variables. Why do you need that?","issue_id":1660325302374,"origin_id":391244063,"user_origin_id":439571,"create_time":1527059469,"update_time":1527059492,"id":1669614811709,"updated_at":"2022-11-28T05:53:31.709000Z","created_at":"2022-11-28T05:53:31.709000Z"},{"_id":"63844cdb4b97542c9a355dd9","body":"Hey @tomasbjerre , I see this conversation tailed off, but I am looking to use variables in the regexp field because I'm trying to only send a notification when the person clicking the button is _not_ the author of the pull request itself.\r\n\r\nIs there another way of achieving that functionality without using the regexp field?","issue_id":1660325302374,"origin_id":542778426,"user_origin_id":29339252,"create_time":1571242426,"update_time":1571242426,"id":1669614811713,"updated_at":"2022-11-28T05:53:31.713000Z","created_at":"2022-11-28T05:53:31.713000Z"},{"_id":"63844cdb4b97542c9a355dda","body":"Sounds like a valid use case.","issue_id":1660325302374,"origin_id":542782255,"user_origin_id":439571,"create_time":1571242960,"update_time":1571242960,"id":1669614811716,"updated_at":"2022-11-28T05:53:31.715000Z","created_at":"2022-11-28T05:53:31.715000Z"},{"_id":"63844cdb4b97542c9a355ddc","body":"Hi,\r\n\r\nI would like to trigger Jenkins when ${PULL_REQUEST_TO_BRANCH} = feature\/ANZIDTPM-QA\r\n\r\nhow to set the filter?","issue_id":1660325302374,"origin_id":788897869,"user_origin_id":39217044,"create_time":1614690655,"update_time":1614690655,"id":1669614811720,"updated_at":"2022-11-28T05:53:31.719000Z","created_at":"2022-11-28T05:53:31.719000Z"}]

Hi, I'd like to implement a notification which is only started, when the ${PULL_REQUEST_TO_BRANCH} is a specific branch of my repository. E.g. to send notifications of all PRs to the...

skarfiol

Update plugin 4.1 to 5.0

[{"_id":"638445ea5ae95c7a2234b6ae","body":"It seems we found the reason: it's the context.\r\nOur system has an address https:\/\/my_url\/stash \r\n@sreer-pega @sreer I would like to understand why it is removed contextPath in https:\/\/github.com\/tomasbjerre\/pull-request-notifier-for-bitbucket\/commit\/7de2b9c500cbe8a30a57872acd3c72ad27cf932c\r\nIs it possible to return contextPath ?","issue_id":1660325302376,"origin_id":762735045,"user_origin_id":77663430,"create_time":1611050391,"update_time":1611050391,"id":1669613034394,"updated_at":"2022-11-28T05:23:54.393000Z","created_at":"2022-11-28T05:23:54.393000Z"},{"_id":"638445ea5ae95c7a2234b6af","body":"@nenashev-ve You could try getting back context path. However, let me add that during my testing the context-path was not available. I am not the owner of the code but a consumer of the plugin just like you. This is the code that worked for us with BB7. Hence I shared it to the main repository. You could go ahead and make the changes and try to run in your setup. If everything works you could create a PR.","issue_id":1660325302376,"origin_id":762744174,"user_origin_id":63645034,"create_time":1611051328,"update_time":1611051328,"id":1669613034398,"updated_at":"2022-11-28T05:23:54.397000Z","created_at":"2022-11-28T05:23:54.397000Z"},{"_id":"638445ea5ae95c7a2234b6b0","body":"We've ran into the same issue. I did not find out how to re-add the contextPath as a variable, so ended up changing all this URL's to include the context as a fixed string. For example: \r\n\r\nOld 4.1 release:\r\nvar settingsAdminUrlPostUrl = contextPath + \"\/rest\/prnfb-admin\/1.0\/settings\";\r\n\r\nCurrent 5.0 release:\r\nvar settingsAdminUrlPostUrl = \"\/rest\/prnfb-admin\/1.0\/settings\";\r\n\r\nMy build of the plugin:\r\nvar settingsAdminUrlPostUrl = \"\/bitbucket\/rest\/prnfb-admin\/1.0\/settings\";\r\n\r\nThis is not a pull request worthy solution, but maybe it can help for you too @nenashev-ve ?","issue_id":1660325302376,"origin_id":782030472,"user_origin_id":4362619,"create_time":1613735869,"update_time":1613735869,"id":1669613034401,"updated_at":"2022-11-28T05:23:54.401000Z","created_at":"2022-11-28T05:23:54.401000Z"}]

After updating the plugin to 7.6.1 After updating the plugin on 7.6.1, I could not go to the plugin configuration page, in every PR I saw this error, after the...

nenashev-ve

Slow Button Rendering

[{"_id":"638446024b97542c9a355132","body":"@mirceapopro have you found a solution so far?\r\n","issue_id":1660325302380,"origin_id":581848439,"user_origin_id":874102,"create_time":1580813093,"update_time":1580813093,"id":1669613058902,"updated_at":"2022-11-28T05:24:18.901000Z","created_at":"2022-11-28T05:24:18.901000Z"},{"_id":"638446024b97542c9a355133","body":"@r4d1um unfortunately we have not.","issue_id":1660325302380,"origin_id":775852920,"user_origin_id":22717671,"create_time":1612868072,"update_time":1612868072,"id":1669613058908,"updated_at":"2022-11-28T05:24:18.908000Z","created_at":"2022-11-28T05:24:18.908000Z"}]

Hi Tomas, I have noticed in the logs a lot of entries related to button. We have only 1 button in each repository and each time we open a pull...

mirceapopro

Question: about the headers in bitbucket

[]

How were you able to get the header data https://confluence.atlassian.com/bitbucketserver077/event-payload-1026551357.html into the environment of the build server? I have only ever been able to accomplish this using jenkins + the...

wjohnston-sfdc

Is there a plan for support DC version?

[{"_id":"6384493dbc25e83db00f2afb","body":"No, unfortunately not. See https:\/\/community.developer.atlassian.com\/t\/eula-and-data-center-for-free-apps\/26062","issue_id":1660325302387,"origin_id":708058600,"user_origin_id":2417004,"create_time":1602630731,"update_time":1602630731,"id":1669613885906,"updated_at":"2022-11-28T05:38:05.906000Z","created_at":"2022-11-28T05:38:05.906000Z"}]

Great plugin.Thanks. Is there a plan for support DC version?

yamazakei321

Trigger Button not appearing in Pull Requests

[{"_id":"63844b804b97542c9a355b13","body":"@tomasbjerre any help here ?","issue_id":1660325302391,"origin_id":624438187,"user_origin_id":12809083,"create_time":1588740121,"update_time":1588740121,"id":1669614464308,"updated_at":"2022-11-28T05:47:44.307000Z","created_at":"2022-11-28T05:47:44.307000Z"},{"_id":"63844b804b97542c9a355b14","body":"Have you checked the `Everyone` radio button in the button config?","issue_id":1660325302391,"origin_id":686438796,"user_origin_id":153960,"create_time":1599134153,"update_time":1599134153,"id":1669614464312,"updated_at":"2022-11-28T05:47:44.311000Z","created_at":"2022-11-28T05:47:44.311000Z"}]

A configured button is not visible in certain Pull Requests. And its not consistent in its behaviour. I couldnt find any errors in the logs. Plugin version - 4.1 BB...

senaraya

Configuration UI is broken - Uncaught Error: plugin/prnfb/admin missing aui

[{"_id":"638449454b97542c9a355737","body":"Install latest version of the plugin.\r\n\r\nSee: https:\/\/github.com\/tomasbjerre\/pull-request-notifier-for-bitbucket\/issues\/321\r\n","issue_id":1660325302398,"origin_id":522949237,"user_origin_id":439571,"create_time":1566296007,"update_time":1566296019,"id":1669613893613,"updated_at":"2022-11-28T05:38:13.612000Z","created_at":"2022-11-28T05:38:13.612000Z"},{"_id":"638449454b97542c9a355738","body":"We already are on 4.1, the issue is still happening.","issue_id":1660325302398,"origin_id":523328932,"user_origin_id":439587,"create_time":1566371609,"update_time":1566371726,"id":1669613893616,"updated_at":"2022-11-28T05:38:13.616000Z","created_at":"2022-11-28T05:38:13.616000Z"},{"_id":"638449454b97542c9a355739","body":"I am able to use the global, project and repo -level configuration pages in Bitbucket Server v6.5.1.\r\n\r\nI made the test with this configuration: https:\/\/github.com\/tomasbjerre\/bitbucket-server-jenkins-release-tags","issue_id":1660325302398,"origin_id":523476630,"user_origin_id":439571,"create_time":1566396956,"update_time":1566396956,"id":1669613893619,"updated_at":"2022-11-28T05:38:13.619000Z","created_at":"2022-11-28T05:38:13.619000Z"},{"_id":"638449454b97542c9a35573a","body":"I tried with a completely fresh project and repo and get the error immediately. Maybe the error will go away when we update bitbucket to v6.5.1","issue_id":1660325302398,"origin_id":523487570,"user_origin_id":439587,"create_time":1566398422,"update_time":1566398422,"id":1669613893622,"updated_at":"2022-11-28T05:38:13.621000Z","created_at":"2022-11-28T05:38:13.621000Z"},{"_id":"638449454b97542c9a35573b","body":"Bitbucket Server 6.6.1 and seeing this error","issue_id":1660325302398,"origin_id":535969857,"user_origin_id":5199836,"create_time":1569595442,"update_time":1569595442,"id":1669613893625,"updated_at":"2022-11-28T05:38:13.624000Z","created_at":"2022-11-28T05:38:13.624000Z"},{"_id":"638449454b97542c9a35573c","body":"Looks like AUI was updated from 7 to 8 in Bitbucket Server 6:\r\nhttps:\/\/developer.atlassian.com\/server\/bitbucket\/reference\/api-changelog\/\r\n\r\nAnd that is documented here:\r\nhttps:\/\/docs.atlassian.com\/aui\/8.0.0\/docs\/upgrades\/aui-8.html\r\n\r\nThe new API is documented here:\r\nhttps:\/\/docs.atlassian.com\/aui\/8.5.1\/docs\/helper.html\r\n\r\nAnd that means, the js-files:\r\nhttps:\/\/github.com\/tomasbjerre\/pull-request-notifier-for-bitbucket\/tree\/master\/src\/main\/resources\r\nCannot require `@atlassian\/aui`.\r\n\r\nIt is really strange that this does not happen to me when I use Bitbucket Server 6. I also tried 6.5.1.\r\n\r\nI test it like this:\r\n\r\n * `docker run -p 7990:7990 atlassian\/bitbucket-server`\r\n * Upload the 4.1 release\r\n * Browse to http:\/\/localhost:7990\/plugins\/servlet\/prnfb\/admin\r\n * I can save all kinds of configuration\r\n\r\nYou can check what version of AUI you are using, by hitting F12 in Chrome and check the body-tag:\r\n\r\n\r\n","issue_id":1660325302398,"origin_id":536024403,"user_origin_id":439571,"create_time":1569604431,"update_time":1569608391,"id":1669613893629,"updated_at":"2022-11-28T05:38:13.628000Z","created_at":"2022-11-28T05:38:13.628000Z"},{"_id":"638449454b97542c9a35573d","body":"Opened an issue here: https:\/\/community.developer.atlassian.com\/t\/how-to-get-ajs-contextpath-in-aui-8\/32202","issue_id":1660325302398,"origin_id":536050355,"user_origin_id":439571,"create_time":1569609008,"update_time":1569609008,"id":1669613893631,"updated_at":"2022-11-28T05:38:13.631000Z","created_at":"2022-11-28T05:38:13.631000Z"},{"_id":"638449454b97542c9a35573e","body":"> Bitbucket Server 6.6.1 and seeing this error\r\n\r\nSorry @tomasbjerre, my bad, all seems working with BBS 6.6.1. We had the outdated plugin from Atlasssian Marketplace. When we installed the latest version from github releases, the issue has disappeared.","issue_id":1660325302398,"origin_id":536091388,"user_origin_id":5199836,"create_time":1569617271,"update_time":1569617271,"id":1669613893633,"updated_at":"2022-11-28T05:38:13.633000Z","created_at":"2022-11-28T05:38:13.633000Z"},{"_id":"638449454b97542c9a35573f","body":"Hm, we just updated to 6.6.1 and the issue still happens for us :\/","issue_id":1660325302398,"origin_id":536434622,"user_origin_id":439587,"create_time":1569827751,"update_time":1569827751,"id":1669613893636,"updated_at":"2022-11-28T05:38:13.636000Z","created_at":"2022-11-28T05:38:13.636000Z"},{"_id":"638449454b97542c9a355741","body":"Upgraded to Atlassian Bitbucket v6.9.1 and still seeing the issue. ","issue_id":1660325302398,"origin_id":681072373,"user_origin_id":42221511,"create_time":1598469327,"update_time":1598469327,"id":1669613893640,"updated_at":"2022-11-28T05:38:13.639000Z","created_at":"2022-11-28T05:38:13.639000Z"}]

We are no longer able to configure the plugin from its configuration UI. The notifications we have configured in the past continue to work, but the configuration UI is broken...

romandecker