Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira feature: 

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1845

...

Dates: January 17, 2024 to January 24, 2024

Slack channel for UAT questions and discussion: #acquisitions-uat

Related videos

UAT Overview

...

Known Issues

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryissuetype = Bug AND issuekey in linkedissues("UXPROD-1018")
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

...

  1. Navigate to receiving app
  2. Search for the receiving title of the order you created (Try searching by order number if needed)
  3. Create 5 piece records each with a different enumeration and expected receipt (Use today's date for piece 1-5 and add +1 day for each piece created after those 5, if desired)
  4. Edit piece 4 and set the status to unreceivable
  5. Select piece 5 and set the status to Claim sent, adding internal and external notes as desired, set the date to tomorrow
  6. Feel free to add additional pieces and experiment more but do not edit pieces 1-5
  7. Break for the day
  8. Return on day 2 to find piece number 1-3 now have a status of "Late"
    1. Select piece 2 and use the delay claim action setting tomorrow as the date
  9. Return on day 3 to find piece 5 now has a status of Late'
    1. Select piece pieces 1-5 and review the Status log details to make sure they are accurate based on the edits you made

...