Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Count of loans not anonymized because of associated fee/fines not displayed

Description

Overview:
Steps to Reproduce:

  1. Log into https://bugfest-juniper.folio.ebsco.com/

  2. Find user with closed loans, some of which have fees or fines associated with them

  3. In closed loans display, click on anonymize all loans

Expected Results: anonymized loans removed from display
loans with fee/fines remain in display
loans anonymized message includes count of loans not anonymized
Actual Results: anonymized loans removed from display
loans with fee/fines remain in display
loans anonymized message DOES NOT include count of loans not anonymized
Additional Information:
URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Cheryl Malmborg May 5, 2022 at 7:30 PM

Tested on snapshot.  It looks good.

Artem Blazhko May 5, 2022 at 9:06 AM

Hello . Bug already fixed and new functionality is available here - https://folio-snapshot.dev.folio.org/

Cheryl Malmborg May 3, 2022 at 8:47 PM

The wording you found is better.  Use it:

"<number> loan(s) had associated fees/fines and could not be anonymized."

Artem Blazhko May 3, 2022 at 1:22 PM

Hello . I have found the initial message in the file with translations and it has the following structure:

"<number> loan(s) had associated fees/fines and could not be anonymized."

Previously you confirmed that we should use the "Anonymization prevented for <number> loan(s)" message.

Sorry for asking the same question but could you clarify what approach will be better?

Cheryl Malmborg April 27, 2022 at 7:19 PM

Yes, "Anonymization prevented for <number> loan(s)" is fine.

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Vega

Parent

Fix versions

Release

Morning Glory (R2 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 5, 2021 at 6:21 PM
Updated June 27, 2022 at 7:46 PM
Resolved May 6, 2022 at 12:59 PM
TestRail: Cases
TestRail: Runs