See work orders with failed run attempts
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
The work order status displayed on the history page shows the final state of the latest run associated with the work order. Whilst this is good, when debugging retrospectively, it is useful for users to be able to filter for runs that have failed previously even if the latest run is successful. This is currently impossible unless the user has the URL of the failed run.
To fix this, we want a new run status filter that allows users to filter work orders by the final state run attempts. i.e. Show me work orders with one or more runs with a failed or crashed final state even though the latest state is successful.
In the future, we'd like a way to show previous runs in the collapsed view of a work order. Consider implementing something like the dots below, or break it out into a new issue if required:
- Allow users to see the state of the last five runs associated with a work order on the history page.
See the image below, there are dots of different colors that show the final state of the last five runs in a work order. The dots should not show if there is ONLY one run attempt in the work order.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the history page and trace how work-order status filtering currently uses the latest run. Add a filter for work orders with one or more failed or crashed final-state runs, and verify that it also matches work orders whose latest run succeeded. The separate last-five-runs display is future scope and should remain distinct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100