MozillaSecurity / MozillaSecurity/FuzzManager
Template should be associated with a bug provider
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
We don't have a template→provider field, although we do have product/component fields which depend on provider. We should make provider a template field, which means the user default provider is only used when creating new templates or filing a bug without a template.
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 template, provider, product, and component handling in the Python code, then trace template creation and bug filing with and without a template. Done means templates retain their provider, while the user default is used only for new templates or filings without a template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100