Skip to content

Resolve "If some bells are unread, the button is disabled. Same for chat conversation."

ToLei requested to merge 1016-if-some-bells-are-unread-the-button-is-disabled-same-for-chat-conversation into master

Closes #1016 (closed)

What does this MR do?

  • Activate the button "Alle als gelesen markieren", if bells or messages are unread.
  • Closes the popup for messages and bells

How confident are you it won't break things if deployed?

I dont know...

Links to related issues

The problem comes into beta with MR: !1736 (merged)

How to test

Steps a reviewer can take to verify that this MR does what it says it does e.g.

  1. Checkout branch locally
  2. Login as foodsaver
  3. Write a message to Bot
  4. Write a message on the store board
  5. Add you to a slot of the store
  6. Login with another foodsaver
  7. Write again a message to Bot
  8. Login with Bot
  9. You should have now 2 unread messages and 2 bells. Click on the messages button.
  10. Click on the new Button "Alle als gelesen markieren" --> All messages should marked as read.
  11. Message popup should be closed.
  12. Click on the bells button.
  13. Click on the new Button "Alle als gelesen markieren" --> All bells should marked as read.
  14. Bell popup should be closed.

Screenshots (if applicable)

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • use "state:" labels to track this MR's state until it was beta tested
  • added an entry to CHANGELOG.md
  • add a short text that can be used in the release notes --> Not needed
  • Once your MR has been merged, you are responsible to create a testing issue in [Beta Testing Repo] (https://gitlab.com/foodsharing-dev/foodsharing-beta-testing):
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...). how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text

(A short text that will appear in the release notes and describes the change for non-technical people. Not always necessary, e.g. not for refactoring.)

Edited by ToLei

Merge request reports