"Severity not set" needinfo sent after 1 week instead of 2
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing the bugbot path that sends the "severity not set" needinfo and identify where the one-week interval is determined. Use the linked Bugzilla example to reproduce or verify the behavior, then confirm that the interval remains two weeks or is configurable per Bugzilla component.
Written by the indexing model from the issue text.
Description
It seems that bugbot has started sending "severity not set" needinfos after 1 week instead of 2 (example).
Our team is already struggling to maintain a 2-week triage response time, so we would prefer that the time period not be reduced to 1 week.
If there's a desire for a shorter time period from other teams, perhaps it can be made configurable per Bugzilla component?
- Dominant language
- Python
- Stars
- 69
- Forks
- 93
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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
Maintainers usually reply within 4 days
-
AttributeError: 'list' object has no attribute 'values'Possibly taken @SAY-5 claimed this 40 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 4 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
mozilla/bugbot#3010 · 1 comment ·
Maintainers usually reply within 4 days
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#13737 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
zhuima/awesome-cloudflare#237 ·
-
Zero-token evaluations are treated as missing cost in selectionPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-research/rrsi#6 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-aws-genai-db-modernizer#294 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4174 ·
Maintainers usually reply within 1 day