Duplicate Fee/Fine Type error message not being cleared after error corrected - PART 1

Description

Overview: This error was discovered when Holly tested the fix for https://folio-org.atlassian.net/browse/UIU-2560#icft=UIU-2560.

Steps to Reproduce:

  1. Log into Morning Glory BugFest as an admin user

  2. Go to Settings/Users/Owners

  3. Create a new Fee/Fine Owner

  4. Go to Settings/Users/Manual charges

  5. Located a Fee/Fine Type already created for the Fee/Fine Owner "Shared" (e.g. Misc fee/fine)

  6. Select your new Fee/Fine Owner from the Fee/Fine Owner drop-down list

  7. Answer "No" to pop-up asking if you want to copy another owner's table entries

  8. Press the NEW button to create a new Fee/Fine Type for the new Fee/Fine Owner

  9. Enter a Fee/Fine Type that already exists for the "Shared" fee/fine owner (e.g. Misc fee/fine)

  10. Error message appears indicating that you are attempting to enter a duplicate

  11. Type over the Fee/Fine Type with a new entry that is not duplicated by the "Shared" Fee/Fine Owner

Expected Results:
No error appears and I am able to save the new Fee/Fine Type

Actual Results:
Previous error message is still displayed, but able to save the new Fee/Fine Type anyway

Additional Information:

Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1
  • 20 Sep 2022, 07:46 PM

Checklist

hide

TestRail: Results

Activity

Show:

Holly MistlebauerSeptember 26, 2022 at 8:11 PM

: I have created https://folio-org.atlassian.net/browse/UIU-2685#icft=UIU-2685 for the second part of the issue. Thanks...

Holly MistlebauerSeptember 26, 2022 at 8:05 PM

Per Artem's recommendation, I have closed this bug ticket and will create a new bug ticket for the second bug described in the attached video. Thanks...

Artem BlazhkoSeptember 21, 2022 at 8:56 AM

Hello .
Thank you for your comment. 
Could you please clarify if it is possible to create a bug for the second part of the issue?
Thank you in advance.

Holly MistlebauerSeptember 20, 2022 at 7:46 PM

: Hi! I just tested this at https://folio-snapshot.dev.folio.org/. The error has two parts, one of which is fixed and one that is not. I have recorded the error that is not fixed and attached the video file UIU-2670.mp4. It may not be possible to fix this error. Please let me know what you discover. Thanks, Holly

Artem BlazhkoSeptember 20, 2022 at 8:37 AM

Hello . Could you check this bug?
New changes are available here - https://folio-snapshot.dev.folio.org/

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Vega

Fix versions

Release

Nolana (R3 2022)

RCA Group

Implementation coding issue

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 23, 2022 at 5:39 PM
Updated October 24, 2023 at 12:36 PM
Resolved September 26, 2022 at 8:05 PM
TestRail: Cases
TestRail: Runs

Flag notifications