Requests in-app report: Requests in transit list
Description
Priority
P3Fix versions
None
Development Team
Prokopovych
Assignee
Tania HewesSolution Architect
None
NoneParent
Parent Field Value
None
Parent Status
None
relates to
Checklist
hideTestRail: Results
Activity
Show:
Cate Boerema March 5, 2019 at 12:05 PM
This seems like a subset of the data in the report defined here: . Closing as a duplicate.
Duplicate
Details
Details
Reporter
Cate BoeremaEstimation Notes and Assumptions
estimates based on other appreport features
Analysis Estimate
Medium < 5 days
Analysis Estimator
Tania HewesFront End Estimate
Medium < 5 days
Front End Estimator
Tania HewesFront-End Confidence factor
Low
Back End Estimate
XL < 15 days
Back End Estimator
Tania HewesRank: FLO (MVP Sum 2020)
R4
Rank: 5Colleges (Full Jul 2021)
R2
Rank: Cornell (Full Sum 2021)
R4
Rank: Chalmers (Impl Aut 2019)
R5
Rank: GBV (MVP Sum 2020)
R2
Rank: hbz (TBD)
R2
Rank: TAMU (MVP Jan 2021)
R2
Rank: Chicago (MVP Sum 2020)
R4
Rank: U of AL (MVP Oct 2020)
R1
Rank: Leipzig (Full TBD)
R1
Rank: Lehigh (MVP Summer 2020)
R4
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 13, 2018 at 5:03 PM
Updated September 16, 2020 at 9:18 PM
Resolved March 5, 2019 at 12:06 PM
TestRail: Cases
TestRail: Runs
Purpose: Institutions that allow items to transit between service points to fill requests will want to run a report periodically - probably daily - that lists items that are in transit to or from a particular service point. The report must contain bib information, item call #, item barcode, etc as well as the service point an item is coming from and when it became in transit. The report is used to track items that are travelling.