[ERM-1249] Saving and/or retrieving LicenseAmendmentStatus records is not always successful Created: 20/Nov/20 Updated: 04/Jan/21 Resolved: 04/Jan/21 |
|
| Status: | Closed |
| Project: | ERM Platform |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Carole Godfrey | Assignee: | Owen Stephens |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | agreements, erm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Sprint: | ERM Sprint 103, ERM Sprint 104 | ||||||||
| Development Team: | Bienenvolk | ||||||||
| Affected Institution: |
Chalmers
|
||||||||
| Description |
|
Overview: Steps to Reproduce:
Repeat the last three steps until you see that even though all amendments were assigned when you saved the agreement (penultimate step), they are reported as not assigned when you view the agreement Expected Results: Additional Information: Interested parties: |
| Comments |
| Comment by Carole Godfrey [ 23/Nov/20 ] |
|
Owen Stephens |
| Comment by Owen Stephens [ 25/Nov/20 ] |
|
Martina Karlsson Carole Godfrey Khalilah Gambrell I'm having difficulty replicating this on https://bugfest-goldenrod.folio.ebsco.com at the moment. Are you able to replicate on there? |
| Comment by Owen Stephens [ 25/Nov/20 ] |
|
Also it would be great to see the bodies of the POST (on duplicating) and PUT (on saving) requests that lead to these situations |
| Comment by Owen Stephens [ 04/Jan/21 ] |
|
The underlying cause is due to an issue with the version of the Grails software framework we were using for mod-agreements 2.x.x (Goldenrod uses a mod-agreements 2.x.x release). As of mod-agreements 3.x.x (used in Honeysuckle) we’ve upgraded to the latest version of the Grails framework and this has fixed the problem going forward. However, it isn’t possible for us to back port this fix to mod-agreements 2.x.x because the solution depends on the new framework - and it simply isn’t possible to retrospectively upgrade 2.x.x to use the newer framework. |