mozilla/mozmoderator

Non-admin users are not able to to enable or disable the "Should this be a moderated event?" functionality

emilghittasv opened this issue · 1 comments

Steps to reproduce
Steps to reproduce the behavior:

For the "Should this be a moderated event?" enabling case (question owner):

  1. Sign in to https://moderator.allizom.org/ with a non admin account.
  2. Create a new event by checking the "Should this be a moderated event?" checkbox.
  3. Click on "edit" button for the event created in step 2.

For the "Should this be a moderated event?" enabling case (question moderator):

  1. Sign in to https://moderator.allizom.org/ with an admin account.
  2. Create a new event but do not check the "Should this be a moderated event?" checkbox and add a non-admin account as the moderator for the event.
  3. Sign in with the non-admin account moderator used in step 2.
  4. Click on the "edit" button for the event created in step 2.
  5. Check the "Should this be a moderated event?" checkbox and click on the "Save" button.
  6. Click on "edit" button for the event created in step 2 again.

For the "Should this be a moderated event?" disabling case (question moderator):

  1. Sign in to https://moderator.allizom.org/ with an admin account.
  2. Create a new event, check the "Should this be a moderated event?" checkbox and add a non-admin account as the moderator for the event.
  3. Sign in with the non-admin account moderator used in step 2.
  4. Click on the "edit" button for the event created in step 2.
  5. Uncheck the "Should this be a moderated event?" checkbox and click on the "Save" button.
  6. Click on "edit" button for the event created in step 2 again.

Expected behavior
Non-admin users are able to enable or disable the "Should this be a moderated event" functionality.

Actual behavior
Non-admin users are unable to enable or disable the "Should this be a moderated event" functionality.

Screencasts
ismoderatedEvent

Additional context
This issue is not reproducible with an admin account.

┆Issue is synchronized with this Jira Story

I can confirm that this issue is verified fixed in stage (all the cases mentioned inside this ticket & the cases mentioned inside the duplicated tickets are no longer reproducible).

Moving this ticket inside the release column.