-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce Regional Staff Group Permissions #3493
base: 3385-regional-staff-submission-history
Are you sure you want to change the base?
Reduce Regional Staff Group Permissions #3493
Conversation
- Added migration reducing Regional user access - Removed tests since regional users can no longer manipulate other users
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 3385-regional-staff-submission-history #3493 +/- ##
==========================================================================
- Coverage 90.67% 90.63% -0.05%
==========================================================================
Files 311 312 +1
Lines 8923 8936 +13
Branches 680 680
==========================================================================
+ Hits 8091 8099 +8
- Misses 705 709 +4
- Partials 127 128 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary of Changes
Pull request closes #3476
How to Test
OFA Regional Staff
v1/users
only returns your user and not all usersNote: Jan's work in #3385 handles the acceptance criteria related to the frontend. E.g. Regional users cannot submit datafiles and only see submission history for users in their region
Deliverables
More details on how deliverables herein are assessed included here.
Deliverable 1: Accepted Features
Checklist of ACs:
Deliverable 2: Tested Code
CodeCov Report
comment in PR)CodeCov Report
comment in PR)Deliverable 3: Properly Styled Code
Deliverable 4: Accessible
iamjolly
andttran-hub
using Accessibility Insights reveal any errors introduced in this PR?Deliverable 5: Deployed
Deliverable 6: Documented
Deliverable 7: Secure
Deliverable 8: User Research
Research product(s) clearly articulate(s):