Provide count of work orders that had failed but have been fixed in the last week
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Related problem
This feature request comes out of this old issue and this new bug.
It will be too difficult to address the current bug. We think we should ship the fix we have and prioritize this particular bit of information in the digest as a new feature/enhancement because it was never working properly and may be costly to implement.
cc @elias-ba
Description of what the problem is
I want to know how many problematic work orders have been fixed in the last week so that I can... @amberrignell to finish!
Tell us about your idea - describe the solution you'd like.
Add a summary line to the email template (and a related SQL query) to read:
- 4 of these work orders failed initially but were rerun and have now suceeded.
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
Locate the email digest template and the related SQL query described in the issue, then read how failed and rerun work orders are currently counted. Done means the digest includes a summary line reporting work orders that failed initially but were rerun successfully within the last week, with the count backed by the query.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, sql
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100