Project and Repo not shown correctly in dropboxes in global admin GUI

[BrianKrohn]

After upgrading to 3.6 from 3.1 of the add-on, all settings were lost and saving settings doesn't actually save anything. On Bitbucket 5.1.1.

[tomasbjerre]

Have a look at #116 . Some users are confused about having to press the dropdown to see the notifications.

[BrianKrohn]

I got some clarification from the devs that reported this too me. In the Notification section, under Trigger, the Project and Repository dropdowns always say "Any". When you change them and click Save, they revert to "Any".

[tomasbjerre]

This is impossible to work with without you following the issue template. Den 30 juli 2017 18:45 skrev "Brian Krohn" <[email protected]>:

…

I got some clarification from the devs that reported this too me. In the Notification section, under Trigger, the Project and Repository dropdowns always say "Any". When you change them and click Save, they revert to "Any". — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#238 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAa1EwIUh7ipqraKb8DT9Tex-7cNBBUvks5sTLMOgaJpZM4Onq12> .

[BrianKrohn]

Sorry. I am new to this. Where is the template?

[tomasbjerre]

https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/blob/master/ISSUE_TEMPLATE

[tomasbjerre]

Upgrading from Stash to BBS is not something that I will spend time on fixing. And probably not accept a PR for. There are very few users doing that now.

I cannot confirm that "saving settings doesn't actually save anything". I can confirm that the project and repo dropboxes dont get populated correctly. I also see an extra notification being created when I change the project.

[BrianKrohn]

I'm not upgrading from Stash (going from BBS 4.8.4 to 5.1.1) so that's fine. The Project and Repo dropdowns change to "Any" when you attempt to update an existing Notification, so I think that fits your description.

There are no error messages or exceptions in the logs that I could find. I'd be happy to share anything you need. I can also replicate this on my test server, so if there's anything you want me to try, let me know.

[tomasbjerre]

I think this was introduced in 3.5. You may try 3.4 by downloading it from here: https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/releases I think that is the most recent version without this problem.

[tomasbjerre]

The project and repo settings should now be saved correctly. Released in 3.7. Was that all here or are you actually not able to save anything at all?

[BrianKrohn]

My original issue was solved with your note about 116. That's when we found the Project and Repo dropdowns weren't saving when a Notification was updated. I just verified that your change fixed it. Thanks for the quick response and fix. I was not expecting it. I will try to follow your template next time, if we ever come across an issue. Thanks again.

[tomasbjerre]

Great no problem!

[annmcd]

Could you attach an example of saving a new or exsting notificaiton via rest api