Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
customfield_11100 27915
-
Core: F - Sprint 69, Core: F - Sprint 70
-
8
-
Prokopovych
Description
Purpose: Moving a request above a page request with status Open - Not yet filled requires complex special handling (see UIREQ-301) which we would like to circumvent for now by preventing such moves. The purpose of this story is to prevent move above page. We may come back later and support move above page.
Scenarios:
- Scenario
- Given Request A was created at 10:00 am on Item X
- When Request A is moved to Item Y which has item status = Paged because it has also been requested (Request B, created at 10:30 am, Request status = Open - Not yet filled)
- Then:
- Request A should be moved to position 2 of the request queue on Item Y even though it was created first (normally queue of "open - not yet filled" requests is ordered FIFO by create date, but in this case we are making an exception to avoid the complexity of moving above a page)
- A popup should display reading, "Requests cannot be moved above page requests, even when fulfillment hasn't begun. This request will be moved to position 2 in the request queue."
- Request A should be moved to position 2 of the request queue on Item Y even though it was created first (normally queue of "open - not yet filled" requests is ordered FIFO by create date, but in this case we are making an exception to avoid the complexity of moving above a page)
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1653 Move Requests from One Item to Another
-
- Closed
-
- has to be done after
-
CIRC-416 UIREQ-303: Backend for preventing move above page
-
- Closed
-