[SUP-22] Save sometimes does not behave as expected Licenses and Agreements Created: 29/Oct/20 Updated: 29/Mar/21 Resolved: 29/Mar/21 |
|
| Status: | Closed |
| Project: | Support |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Anya | Assignee: | Owen Stephens |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Bienenvolk | ||||||||
| Affected Institution: |
Chalmers
|
||||||||
| Description |
|
Overview: Steps to reproduce: Actual behavior (sometimes) If closing the window with the x in the upper left corner, a duplicate license/agreement is saved or a system error message is displayed Editing a license sometimes results in similar unexpected behavior. After having clicked Save & close, the button remains active. Edits are however saved. The screenshot is an example of what happened when an agreement was saved twice due to the still open full pane and Save-button still active. I can right now only see this error in Firefox but please note that this happens also in Chrome for other users. We have previously reported issues with saving in Organizations app Intrested parties: Marie Widigson |
| Comments |
| Comment by Anya [ 29/Oct/20 ] |
|
Tagging Khalilah Gambrell and Dennis Bridges |
| Comment by Marie Widigson [ 04/Nov/20 ] |
|
Maybe Owen Stephens is interested in this as well? |
| Comment by Anya [ 16/Nov/20 ] |
|
Support sig : Owen Stephens bring this to your awareness... |
| Comment by Anya [ 23/Nov/20 ] |
|
Support sig: Owen Stephens and Khalilah Gambrell - checking in on this... |
| Comment by Owen Stephens [ 25/Nov/20 ] |
|
Anya Khalilah Gambrell Marie Widigson I'm having difficulty replicating this issue on https://bugfest-goldenrod.folio.ebsco.com/ - are you able to replicate on there, or is it only occurring on the Chalmers environment? |
| Comment by Anya [ 07/Dec/20 ] |
|
Marie Widigson are you still getting this error? |
| Comment by Marie Widigson [ 07/Dec/20 ] |
|
Yes, we do. All three of us ERM-colleagues are seeing it from time to time, as late as last week. Anya |
| Comment by Kelly Drake [ 25/Jan/21 ] |
|
Owen Stephens - Support SIG is curious as to if this has been resolved or if we can assist in resolving this? |
| Comment by Owen Stephens [ 25/Jan/21 ] |
|
Hi Kelly Drake and others. So far I've not been able to recreate the problem as described on https://bugfest-goldenrod.folio.ebsco.com and I've not had confirmation that anyone else has been able to do this either. Until I can see this happening it's really hard for us to write up a proper bug for it. What I really need is to be able to recreate this - and until we've done this I'm not sure how we move it forward. For example having the log of the Network requests from the browser leading up to this scenario occurring would be helpful If we have situations where Chalmers are able to recreate the issues persistently then perhaps doing a screenshare with them and being able to see what is going on and ask questions would be helpful - and I’d be happy to do that. I don't know what else to do at this point - we can't progress the investigation or resolution if we can't recreate it (and I've tried extensively) Finally it's probably also worth saying that from Honeysuckle onwards we have upgraded some of the software libraries used in the Agreements and Licenses app, and we know that has resolved some issues that were present in Goldenrod. Unfortunately these changes cannot be back-ported to Goldenrod, so if it turns out this issue is only resolved by the updating of those libraries, we'd have to say we couldn't fix in Goldenrod. I'm only flagging this because this has been the outcome for some of the other Goldenrod support issues and we just need to be mindful of this in terms of time invested in tracking down bugs in Goldenrod. |
| Comment by Marie Widigson [ 26/Jan/21 ] |
|
Hi Owen Stephens& Kelly Drake |
| Comment by Anya [ 01/Mar/21 ] |
|
Marie Widigson -SupportSig: could you verify that this works or doesn't work in Honysuckle. |
| Comment by Anya [ 08/Mar/21 ] |
|
Marie Widigson - could you test to see if this works in Honeysuckle? Thanks |
| Comment by Marie Widigson [ 09/Mar/21 ] |
|
Hi Anya Sorry for the delay in our reply. During the testing in Chalmers Honeysuckle dry run, preparing for the upgrade, we experienced this at a new place: When adding agreement lines from the Agreements app (new functionality as of Honeysuckle). It was the same behavior. We got no visual response when clicking the Save-button. So clicked again. And again. Then closing the window with x. The result was that several identical agreement lines was added to the Agreement. In Honeysuckle, we have not yet experienced the bug in the scenarios originally described. But that does not mean that we are sure that it is gone since it's intermittent and these steps are not made every day. |
| Comment by Anya [ 15/Mar/21 ] |
|
Support: Owen Stephens and Marie Widigson shall we close until it happens again? |
| Comment by Anya [ 22/Mar/21 ] |
|
Support: Marie Widigson// Owen Stephens awaiting your feedback. |
| Comment by Owen Stephens [ 22/Mar/21 ] |
|
Anya that works for me. Thanks |
| Comment by Marie Widigson [ 23/Mar/21 ] |
|
That's ok for us. We will let you know if it happens again. |