Feature ID | Issue ID | Sprint Backlog? | Notes / Estimates / Actions | To be created |
---|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1032 |
---|
|
| | Comparison reports are not loading quickly enough, eg partials. - Consider alternatives to storing large reports, eg,
- potentially chunk up and then paginate the JSON output, similar to eresources?
- stream report outputs?
- What would be the impact to reengineering existing functionality to handle this differently?
- Are there other modules that need to deal with similarly large JSON outputs?
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-879 |
---|
|
| | Duplicate coverage array |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-883 |
---|
|
|
| Code is async based on promises. So fetch doesn't support linear process. Could make this use of endpoints tricky. Relates to Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | CHAL-208 |
---|
| .Ian to discuss with Steve. If progressable potentially with Ethan. |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1004 |
---|
|
| Ethan Freestone | Progressable. Need to work out mod-config |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1037 |
---|
|
| | Investigation piece. If it cannot be fixed, remove the sort options from the UI. |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1039 |
---|
|
| | Done and done. |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1040 |
---|
|
| | Ready to progress |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1041 |
---|
|
| | To be fixed in stripes. Then requires a review of ERM apps for replacement calendar widget, specifically where date picker is used within card component. |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1050 |
---|
|
| |
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1051 |
---|
|
| |
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1052 |
---|
|
| Claudia Malzer |
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1043 |
---|
|
| | Change agreement search to unlink Organisation and Content Provider filters. Maybe affected by https://folio-project.slack.com/archives/CAYCU07SN/p1595238491191800 |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1044 |
---|
|
| | Simple change to extend matched fields for Search |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1045 |
---|
|
| Claudia Malzer | Simple change to extend matched fields for Search |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-2267 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-2335 |
---|
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1046 |
---|
|
| | Should be able to progress a solution (if not a perfect or FOLIO wide solution) |
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-1759 |
---|
|
| | | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1048 |
---|
| / Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1047 |
---|
|
Could do with technical review and assess approach. Best to leave until II and OS return |
UX Improvements |
|
|
|
Comparisons Feedback |
|
|
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-742 |
---|
|
| | Potentially transfer to Ethan ... |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-780 |
---|
|
| | Compare with ERM-815. Check backend can sort as part, but not expecting backend changes to be made as part of this. |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1016 |
---|
|
| | To pick up as alongside of ERM-1000 |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-932 |
---|
|
| |
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-1058 |
---|
|
| |
|