Agreements
(UXPROD-573)
|
|
| Status: | Draft |
| Project: | ERM Platform |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Agreements |
| Type: | Story | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | Owen Stephens |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | erm, resourcemanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Bienenvolk | ||||||||
| Epic Link: | Agreements | ||||||||
| Description |
| Comments |
| Comment by Khalilah Gambrell [ 10/Dec/19 ] |
|
Marie Widigson, feature created. Jag Goraya and Owen Stephens, please let me know if I should change any team assignment, etc. |
| Comment by Owen Stephens [ 07/Feb/20 ] |
|
Hey Khalilah Gambrell Marie Widigson I've moved this and modified it a bit - hope this is ok. Currently we have an export of agreements that includes Orgs and Licenses (in the Action menu from an agreement choose "Export"), so the issue is the inclusion of the eholdings app resources. At the moment we just pump out an UUID for these in the export - I think we need to work out what is required here, and what is practically possible (as Agreements only has minimal information about eHoldings resources What information would you expect to be included about the eholdings resources in the scenario where:
|
| Comment by Owen Stephens [ 07/Feb/20 ] |
|
also looping in steve.osguthorpe to advise on what's practical here - as I suspect this is going to be the real limiting factor to be honest |