|
Issue links:
|
Defines
|
|
defines
|
UXPROD-775
|
Tags - Central Management
|
Analysis Complete
|
Relates
|
|
relates to
|
UXPROD-3006
|
Courses: Implement Tags for Courses
|
Open
|
|
relates to
|
UXPROD-3007
|
Courses: Implement Tags for Course Re...
|
Open
|
|
| Release: |
Not Scheduled
|
| Epic Link: |
Tags - Central Management
|
| Analysis Estimate: |
Medium < 5 days
|
| Analysis Estimator: |
Ann-Marie Breaux (Inactive)
|
| Front End Estimate: |
Medium < 5 days
|
| Front End Estimator: |
Zak Burke
|
| Back End Estimate: |
Large < 10 days
|
| Back End Estimator: |
Heikki Levanto
|
| Estimation Notes and Assumptions: |
UXPROD-258: the "edit" and "merge" permissions are interesting because if we are implementing those operations through mass-edit (and that's the assumption in UXPROD-257) the user effectively needs permissions to edit tagged records. Are we okay with a solution where those permissions need to be explicitly assigned to the user (otherwise the edit/merge operation fails) or do we need to resort to some "module permission" magic?
|
| Development Team: |
None
|
| Kiwi Planning Points (DO NOT CHANGE): |
1
|
| PO Rank: |
59
|
| PO Ranking Note: |
None of Tags-Central Management Epic marked po-mvp since only 1 library has ranked any issues as go-live
|
| Rank: Chalmers (Impl Aut 2019): |
R4
|
| Rank: Chicago (MVP Sum 2020): |
R4
|
| Rank: Cornell (Full Sum 2021): |
R4
|
| Rank: Duke (Full Sum 2021): |
R4
|
| Rank: 5Colleges (Full Jul 2021): |
R4
|
| Rank: FLO (MVP Sum 2020): |
R4
|
| Rank: GBV (MVP Sum 2020): |
R2
|
| Rank: hbz (TBD): |
R2
|
| Rank: Hungary (MVP End 2020): |
R1
|
| Rank: Lehigh (MVP Summer 2020): |
R4
|
| Rank: Leipzig (Full TBD): |
R2
|
| Rank: Leipzig (ERM Aut 2019): |
R2
|
| Rank: MO State (MVP June 2020): |
R4
|
| Rank: TAMU (MVP Jan 2021): |
R4
|
| Rank: U of AL (MVP Oct 2020): |
R2
|