Set status and `Ever confirmed` on confirmation
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Start at bugmon's bug-confirmation flow and inspect how it updates Bugzilla bugs. Confirm that an UNCONFIRMED bug becomes NEW and that the Ever confirmed flag is set, then verify both outcomes through the existing confirmation path.
Written by the indexing model from the issue text.
Description
When confirming a bug:
- if the status is UNCONFIRMED, change it to
NEW - set the
Ever confirmedflag
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 1
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 MozillaSecurity/bugmon
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
MozillaSecurity/bugmon#68 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MozillaSecurity/bugmon#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
MozillaSecurity/bugmon#63 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MozillaSecurity/bugmon#60 ·
-
Message: User [:user] <user@mozilla.com> is not currently accepting "needinfo" requests. Code: 32000 Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
MozillaSecurity/bugmon#58 ·
All issues in MozillaSecurity/bugmon
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