Consider adding text asking the reporter "the last version of Firefox which did not have this issue" for bugs created by reporters who dont have "editbug" access
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Intention: To know if the reporters issue is a regression, or is a new bug. And to reduce the manual effort of devs/triage folks in asking the reporter for this information
Where a "new" reporter has filed a bug, ask them if "Did this ever work in a previous version of Firefox". A proxy for "new" reporter can be a user who does not have "editbugs" access.
Potential risk: Reporter may think that Mozilla is pushing them to do work.
Counter point: It is fair to assume that a user advanced enough to file a bug on bmo would understand that without basic information from them, Firefox with its large/complex code and interaction with OS/Drivers/external software/customizations needs some basic information to diagnoise issues.
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 by locating the bug-creation flow and the logic that identifies reporters without editbugs access. Add the proposed regression-history question for those reporters, while considering the stated risk that it may feel burdensome; done means the question appears only for the intended reporters and its wording is covered by tests.
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