Licenses
(UXPROD-574)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q1 2019 | Parent: | Licenses |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Owen Stephens | Assignee: | Owen Stephens |
| Resolution: | Done | Votes: | 0 |
| Labels: | crossrmapps, erm, licenses, resourcemanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Epic Link: | Licenses | ||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||||||||||||||
| Rank: 5Colleges (ERM Jun 2020): | R1 | ||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||
| Description |
|
Enable the addition of organisations to licenses with different roles.
Roles:
Out of scope:
TBC whether implementation will initially support Organisations are shared between Folio apps within a tenant implementation |
| Comments |
| Comment by md331 (Inactive) [ 06/Feb/19 ] |
|
There's currently some debate about how the list of organisations to select from will be managed by the backend. An identical feature already exists for Agreements which users can assign organisations to, and the backend for that is in place. So the question when designing the backend for this is: Should the organisation management used in mod-agreements be generalised so that it can be used by ui-licenses? Required for Generalising the Existing Code (non-exhaustive)
Issues with Maintaining Separate Lists
|