OpenFn / OpenFn/lightning

Allow user to limit search for last run per work order

Open
#593 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

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".
image (2).png

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the searchbar and trace how search requests are handled for work orders and their runs. Use the two user-acceptance scenarios as checks: selecting the option excludes matches from earlier runs, while leaving it unselected includes them.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
full-stack, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.