issue-detail: link to regzbot ingested issues
Open
Backend
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
Once Regzbot ingests the KernelCI `[REGRESSION]` reports in the mailing list, we should update the Issue in the DB with a reference to it, such that we become able to compute how useful those reports are.
Somewhat related to storing the reference for the reports in the DB: https://github.com/kernelci/dashboard/issues/1959
Contributor guide
Research direction
Start by tracing where Regzbot-ingested KernelCI reports enter the dashboard and how Issues are stored in the database. Review the related issue #1959; done means each ingested [REGRESSION] report is referenced from its Issue so report usefulness can be computed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100