Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
-
ERM Sprint 72, ERM Sprint 73, ERM Sprint 74, ERM Sprint 75, ERM Sprint 76
-
Bienenvolk
Description
Resources can have a date that they joined or left a package (access_start and access_end dates respectively). The current content of a package should only be considered to be the resources that have an access_start date in the past (or empty) or an access_end date in the future (or empty).
By default the user should only ever see the list of current resources in a package in the UI and exports.
This story is to implement appropriate filters so that only current content of a package is displayed by default
Out of scope is viewing the lists of resources that previously were part of a package (but have now left) or are schedule to join a package in the future (these other filters are the subject of ERM-396)
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-585 Track changes to eresources
-
- Closed
-
- relates to
-
ERM-551 Endpoints like future, dropped etc not working for agreements
-
- Closed
-
-
ERM-556 It should not be possible to set accessStart later than accessEnd on PCI
-
- Closed
-
- requires
-
ERM-395 Populate access start and access end dates
-
- Closed
-