[ERM-2506] Display licenses sorted in predictable order in Agreements Created: 30/Nov/22  Updated: 03/May/23  Resolved: 03/May/23

Status: Closed
Project: ERM Platform
Components: ui-agreements
Affects versions: None
Fix versions: None

Type: Story Priority: TBD
Reporter: Masami Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: Support, erm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines ERM-2660 ui-agreements release. Fix version: 1... Closed
Sprint: ERM Sprint 162, ERM Sprint 160, ERM Sprint 161, ERM Sprint 163, ERM Sprint 164, ERM Sprint 159
Development Team: Bienenvolk
Release: Poppy (R2 2023)
RCA Group: TBD

 Description   

Purpose:
Within an Agreement, linked licenses can display as "Historical", "Future" or "Controlling". Currently the order that the licenses display in is not controlled. This story is to make t he ordering consistent and predictable

User story statement(s):

As a librarian
I want to view an agreement and linked licenses in a consistent order
so that I can easily navigate the list of linked licenses

Scenarios:

  1. Scenario:
    • Given an agreement with multiple linked licenses with status within agreement "Future"
    • When I view the agreement
    • Then the licenses with status within agreement "Future" are sorted by (in order):
      • license start date (the earliest date first)
      • license end date (the earliest date first)
      • name
  2. Scenario:
    • Given an agreement with multiple linked licenses with status within agreement "Historical"
    • When I view the agreement
    • Then the licenses with status within agreement "Historical" are sorted by (in order):
      • license start date (the latest date first)
      • license end date (the latest date first)
      • name

Other information:
If the specific sorts defined above are not possible, we should aim for at least consistency (i.e. the licenses display in the same order every time)

Interested parties:
Kyushu University



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 02/Dec/22 ]

Hi Owen Stephens This was entered into Jira as a bug, and with no dev team. Seems like it should perhaps be a story or feature for Bienenvolk? Please review and update as you see fit. Thank you!

Comment by Owen Stephens [ 02/Dec/22 ]

Thanks Ann-Marie Breaux  - definitely a story for ERM. Have moved into ERM project and will review

Generated at Thu Feb 08 22:22:55 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.