Skip to:

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

Aged to lost action on loan details

Description

Purpose: When an item has aged to lost, reflect this on the loan details & action history for the loan.

  1. Scenario

    • Given a loan for an item that has aged to lost

    • When viewing loan details

    • Then show the aged to lost action in the loan action history

      • Action date: use date and time item aged to lost

      • Action: Aged to lost

      • Due date: same due date as previous row in action history

      • Item status: Aged to lost

      • Source: -

      • Comments: -

  2. Scenario

    • Given a loan for an item that has aged to lost

    • When viewing the loan details

    • Then populate the Lost field with the date and time the item aged to lost
      CB: , in grooming we decided this scenario should be moved to another story. Thanks!

Dev notes

  1. New loan action will be introduced on backend - itemAgedToLost.

  2. Lost date time is specified in loan.agedToLostDate property (draft).

  3. Please also note that the process is executed anonymously by okapi- it means that the aged to lost loan action will have metadata.updatedByUserId undefined.

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Emma BoettcherAugust 19, 2020 at 9:35 PM

Tested on folio-snapshot. As indicated in story comments and discussion, source and comments are not populated for this action.

Emma BoettcherAugust 7, 2020 at 6:26 PM

Yes, it should be consistent. I didn't realize there was already a term for that, and I'll file a separate story.

Cate BoeremaAugust 4, 2020 at 3:53 PM

Hi . Per grooming, we think we can probably display "System" in the Source column, but it would require a separate story and it may have to be a system-wide feature. Also, we noticed that if you look at the record last updated component, you sometimes see "Automated process". Do we want to be consistent?

Cate BoeremaAugust 4, 2020 at 3:47 PM

Estimating just mapping the backend so the action displays in loan action history.

Need to create separate stories for:
1. Populating the Lost field
2. Displaying System or Automated process in Source

Marc JohnsonAugust 4, 2020 at 11:27 AM

Does that mean we are establishing a convention in the reference UI that in the absence of a createdByUserId or updatedByUserId it is assumed that this operation was done by an automated process in the system outside of the context of a user?

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 28, 2020 at 5:22 PM
Updated August 20, 2020 at 11:04 AM
Resolved August 19, 2020 at 9:35 PM
TestRail: Cases
TestRail: Runs