Nag when somebody sets a bug as being a regression and adds a bug to its blocks or depends_on fields
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
This is to ensure people use regressed_by instead of blocks or depends_on.
We should nag when somebody sets 'Is Regression' to 'yes' or 'Has Regression Range' to 'yes' or 'no', and at the same time they add a bug to "blocks" or "depends_on".
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
No files, tests, or entry points are named in the issue. Start by locating the Bugzilla metadata handling for “Is Regression,” “Has Regression Range,” blocks, depends_on, and regressed_by; done means a nag is sent when the specified regression fields and bug relationships are set together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100