Closed Bug 249417 Opened 21 years ago Closed 21 years ago

FAQ: Help fix bugs, check for bugs link lists only bugs re-assigned to Nobody.

Categories

(Calendar :: Website, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gekacheka, Assigned: mostafah)

References

()

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 The FAQ "How can I help fix bugs?" currently says "1. Check the list of _unassigned bugs_ that are in Bugzilla." But the link given only lists bugs assigned to Nobody. As I understand: Newly created bugs are by default 'Assigned-to' Mostafah as owner of the calendar project, but their status is 'New' rather than 'Assigned', meaning that Mostafah has not accepted the bug. Bugs are re-assigned to Nobody when (a) a bug was accepted by somebody, setting its 'Assigned-to' to that somebody and its status to 'Assigned', but then (b) that somebody can no longer work on the bug, so they re-assign it to Nobody, and its status becomes 'New'. (is this correct?) Therefore, listing only Nobody bugs is an incomplete list of bugs available for work. A list of bugs with status 'New' would be more appropriate than the list of Nobody bugs. A better or additional link may be the calendar bugs.html page. It gives several links for listing calendar bugs, and also explains how to help triage bugs. Reproducible: Always Steps to Reproduce: 1. 2. 3.
(In reply to comment #0) > As I understand: > > Newly created bugs are by default 'Assigned-to' Mostafah as owner of the > calendar project, but their status is 'New' rather than 'Assigned', meaning that > Mostafah has not accepted the bug. Bugs are re-assigned to Nobody when (a) a > bug was accepted by somebody, setting its 'Assigned-to' to that somebody and its > status to 'Assigned', but then (b) that somebody can no longer work on the bug, > so they re-assign it to Nobody, and its status becomes 'New'. > > (is this correct?) This is correct and the link is definitely not correct
1. change link to point to bugs.html, where it also explains bugzilla a little 2. add "not required" (contributors might not have bugzilla authority to change assignment, but that should not stop them) 3. clarified which steps occur using Bugzilla.
Checked in. Thanks
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
QA Contact: help-documentation
The bugspam monkeys have been set free and are feeding on Calendar :: Website. Be afraid for your sanity!
QA Contact: help-documentation → website
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: