Calculate tag statistics taking into account duplicate bugs too
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start with auto_nag/scripts/pdfjs_tag_change.py at the referenced revision and trace how unresolved bugs contribute to tag statistics. Check how duplicate counts are represented for each bug, then update the calculation so a bug contributes its duplicate count rather than only one. Done means tag statistics include duplicates while retaining the existing unresolved-bug scope.
Written by the indexing model from the issue text.
Description
In https://github.com/mozilla/relman-auto-nag/blob/d5c923cc599895acc2ea03adb899271df1f2ae95/auto_nag/scripts/pdfjs_tag_change.py, we only take into account unresolved bugs, but for tag statistics when we encounter a given bug we want to increase the number associated to the bug tags by the number of its duplicates and not just by 1.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
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.
More from mozilla/bugbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100