Skip to content

Additional GOALS Groups created and permission adjusted

- requested to merge GOALS into master

Closes ___

What does this MR do?

additional Workgroup functions are introduced.

	public const STORE_COORDINATION = 4; // Betriebskoordinationsteam
	public const REPORT = 5; // Meldebearbeitungsteam
	public const MEDIATION = 6; // Mediationsteam
	public const ARBITRATION = 7; // Schiedsstelle
	public const FSMANAGEMENT = 8; //Foodsaververwaltung
	public const PR = 9; // Öffentlichkeitsarbeit
	public const MODERATION = 10; // Moderationsteam

following administration rights are given to admins of respective group. These apply to the region they are attached to. See documentation for description : https://docs.google.com/presentation/d/1Ul3hc0pJVxjnGgz3hXD-jAXg1eXRjSRe2wI9ATruu24/edit#

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

Kind of

Links to related issues

https://docs.google.com/presentation/d/1Ul3hc0pJVxjnGgz3hXD-jAXg1eXRjSRe2wI9ATruu24/edit#

How to test

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

For each workgroupfunction users are created

        public const STORES_COORDINATION = 4; // Betriebskoordinationsteam = userstoregroup1@example.com
	public const REPORT = 5; // Meldebearbeitungsteam = userreport1@example.com
	public const MEDIATION = 6; // Mediationsteam = usermediation1@example.com
	public const ARBITRATION = 7; // Schiedsstelle = userarbitration1@example.com
	public const FSMANAGEMENT = 8; //Foodsaververwaltung = userfsmanagement1@example.com
	public const PR = 9; // Öffentlichkeitsarbeit = userpr1@example.com
	public const MODERATION = 10; // Moderationsteam = usermoderation1@example.com

testing of storecoordinationadmin:

  1. Checkout branch locally
  2. Login as userstoregroup1@example.com
  3. Find a store you are not store manager of (over map or storelist) and store must belong to the district.
  4. You should be able to look into the store and administer it (edit, approve,change team etc.)
  5. Logout user
  6. Login as userbot@example.com
  7. Find a store you are not storemanager of and store must belong to the district.
  8. You are not able to administer it
  9. Logout

testing of ReportGroup:

  1. Checkout branch locally
  2. Login as userbot@example.com
  3. go to profile page of any user in Göttingen district (who is not an admin of Meldebearbeitung)
  4. have popup on how to make a report about user
  5. send report
  6. Logout
  7. Login as userreport1@example.com
  8. Go in the Menue to "bezirke-Göttingen-Meldungsansicht (LMG)"
  9. see in the overview the report you created.

testing of ArbitrationGroup:

  1. Checkout branch locally
  2. Login as userbot@example.com
  3. go to profile page of a user that is admin of the report group (Meldebearbeitungsteam) of Göttingen
  4. have popup on how to make a report about user
  5. send report
  6. Logout
  7. Login as userarbitration1@example.com
  8. Go in the Menue to "bezirke-Göttingen-Meldungsansicht (LS)"
  9. see in the overview the report you created.
  10. Don't see any other reports of other "normal" useres of göttingen

testing of mediation request:

  1. Checkout branch locally
  2. Login as userbot@example.com
  3. go to any profile
  4. click on "mediation anfragen"
  5. See popup

testing of Moderation:

  1. Checkout branch locally
  2. go to database and make göttingen a moderated forum (fs_bezirk - moderated = 1 )
  3. Login as userbot@example.com
  4. create a thread in the göttingen forum
  5. see that "your thread was send for admission"
  6. Go to e-mail server
  7. see email to moderation admins and copy link
  8. Login as moderation (usermoderation1@example.com)
  9. Paste link and see the request for new thread
  10. delete or activate thread
  11. go to forum of göttingen and see thread
  12. create forumthread - should be directly visible and no activation required.

the other workgroupfunction (PR, FSManagement) are without function and at the moment can be assigned but don't have any administrative functions.

Screenshots (if applicable)

Any relevant screenshots if this is a design / frontend change

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

Es wurden weitere Gruppenfunktionstypen eingefügt. Eine genaue Beschreibung des GOALS system gibt es hier :https://docs.google.com/presentation/d/1Ul3hc0pJVxjnGgz3hXD-jAXg1eXRjSRe2wI9ATruu24/edit#

Edited by -

Merge request reports