Skip to content

OBLS-837 Fix discrete picking QA findings - #441

Open
olewandowski1 wants to merge 1 commit into
developfrom
OBLS-837-qa-fixes
Open

OBLS-837 Fix discrete picking QA findings#441
olewandowski1 wants to merge 1 commit into
developfrom
OBLS-837-qa-fixes

Conversation

@olewandowski1

@olewandowski1 olewandowski1 commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

https://openboxes.atlassian.net/browse/OBLS-837

Summary

  • Search by product code works. The code was already returned by the API but never indexed, so the placeholder was accurate for names only.
  • Completing a pick returns the picker to the Discrete Picking list instead of the batch "Select Pick Type and Grouping" screen. The session now records which screen it started from.
  • Short picking without a reason code resets the navigation stack instead of pushing, so the finished task is no longer reachable with the back arrow. That path was pushing a screen that is not on the discrete stack, which is why the finished task stayed underneath.
  • One loading indicator per state: skeleton on first load, pull to refresh control for a pull, search bar spinner for background refreshes, and no overlap with the full screen loader when an order is tapped.
  • A partially picked order reads In progress with Lines: 4 / 5 Left, using the order level progress added in the backend PR.
  • "Show assigned orders" is now title cased and sits closer to the queue type chips.
image

Index product codes so search by code works, return the picker to the
screen the session started from instead of the batch pick type screen,
reset the stack on completion so the finished task is no longer reachable
with the back arrow, and show a single loading indicator per state.

Consume the order level pick progress from the pick task API so a
partially picked order reads In progress with the lines left to pick.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant