Set default copy alert permissions
Bug #1811442 reported by
Remington Steed
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
| 3.1 |
Fix Released
|
Medium
|
Unassigned | ||
| 3.2 |
Fix Released
|
Medium
|
Unassigned | ||
| 3.3 |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Copy Alert permissions were added in bug #1768992, but they were not assigned to any permission groups. Currently, staff users can create copy alerts, but they are not able to see what they created (i.e. they don't see any "Existing Alerts" section in the Item Alerts popup).
We should assign the "VIEW_COPY_ALERTS" permission to the "Staff" permission group. Are there other permissions we should assign by default? Bug #1798669 implies that some actions need "ADMIN_COPY_ALERT".
Also, we should do something for those upgrading to Evergreen 3.1:
- Add the permission in a non-intrusive way?
- Add a notice in the upgrade script about how to add the permission?
- At least mention it in the release notes?
| Changed in evergreen: | |
| importance: | Undecided → Medium |
| tags: | added: permissions |
| tags: | added: cataloging |
| Changed in evergreen: | |
| assignee: | nobody → Kyle Huckins (khuckins) |
Revision history for this message
| Kyle Huckins (khuckins) wrote | #2 |
| Changed in evergreen: | |
| assignee: | Kyle Huckins (khuckins) → nobody |
| tags: | added: signedoff |
Revision history for this message
| Galen Charlton (gmc) wrote | #3 |
| Changed in evergreen: | |
| status: | New → Confirmed |
| milestone: | none → 3.3.5 |
| Changed in evergreen: | |
| status: | Confirmed → Fix Committed |
| Changed in evergreen: | |
| milestone: | 3.3.5 → 3.4-rc |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Branch available at https:/