Update for the list of working groups on profile pages
Follow-up from !1988 (merged)
What does this MR do?
- don't show groups to which users have applied but weren't accepted yet (https://foodsharing.freshdesk.com/helpdesk/tickets/1830)
- don't show the empty groups list for foodsharers, because they can't join groups
How confident are you it won't break things if deployed?
Very sure
How to test
First part:
- Checkout branch locally
- Find out in which groups userbot is, e.g. by logging in as userbot or in the
- Login as user2
- Apply to one of those groups
- Check the profile page of userbot that the group to which you applied isn't listed
Second part:
- Login as user1
- Go to any user profile and check that you don't see the list
- Login as any other user (user2, userbot, ...)
- Go to user1's profile and check that you don't see the list
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 -
Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo: - 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.)