You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user that is searching for all work orders that failed due to a specific error (ex: "xx not found"), I would like to limit my search specifically to the last run of each work order, so that I don't get results where the error appeared in a first run but was already resolved.
Details
Below the searchbar, add a checkbox with the label "Only search last run per work order".
When set to true, the search should only apply to the last run each work order.
Implementation notes
Release notes
Users can now (optionally) search across the last runs per work order
User acceptance criteria
given a work order with 2 runs where run 1 (first run) contains a log with the string 'joe' but run 2 (last run) doesn't, when I search for 'joe' and select 'only search on last run, that work order does not appear in the results.
given a work order with 2 runs where run 1 (first run) contains a run log with the string 'joe' but run 2 (last run) doesn't, when I search for 'joe' and unselect 'only search on last run, that work order does appear in the results.
The text was updated successfully, but these errors were encountered:
taylordowns2000
changed the title
Allow user to limit runs search for last attempt
Allow user to limit search for last run per work order
Feb 1, 2024
User story
As a user that is searching for all work orders that failed due to a specific error (ex: "xx not found"), I would like to limit my search specifically to the last run of each work order, so that I don't get results where the error appeared in a first run but was already resolved.
Details
Below the searchbar, add a checkbox with the label "Only search last run per work order".
When set to true, the search should only apply to the last run each work order.
Implementation notes
Release notes
User acceptance criteria
The text was updated successfully, but these errors were encountered: