Bug 995327 - Suggested improvements to Field Descriptions page
Suggested improvements to Field Descriptions page
Status: CLOSED CURRENTRELEASE
Product: Bugzilla
Classification: Community
Component: Documentation (Show other bugs)
4.4
Unspecified Unspecified
low Severity low (vote)
: ---
: ---
Assigned To: Jason McDonald
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-09 01:17 EDT by Jason McDonald
Modified: 2013-09-06 00:14 EDT (History)
3 users (show)

See Also:
Fixed In Version: 4.4.0007
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-06 00:14:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jason McDonald 2013-08-09 01:17:33 EDT
Having reviewed the https://bugzilla.redhat.com/page.cgi?id=fields.html page after Bug 947139 was addressed, I have a couple of suggestions for further improvement.

ASSIGNED Status:

Suggest removing "steps to reproduce the problem".  This should ideally be part of the initial report, that's why it's included in the template text that appears when reporting a new bug.


CANTFIX resolution:

Suggest removing text about the insufficient info and can't reproduce cases.  
These belong under the INSUFFICIENT_DATA resolution. CANTFIX should be used for cases where the bug is permanently blocked (e.g. by an upstream WONTFIX or CANTFIX) or is impractical or unacceptably expensive to fix.




Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:
Comment 2 Suzanne Yeghiayan 2013-08-09 16:14:57 EDT
1.  I'm fine with removing "and steps to reproduce the problem".  The full text for ASSIGNED should be:

  This bug report has been assigned to an engineer. It is well described and
  triaged, but not fixed. It is recommended that the Assigned Engineer add 
  work estimates, risk assessment, and test case. Additional triage can 
  cause a bug report to be reassigned to another engineer or component or 
  moved to CLOSED.  Once a bug report is fixed, it is moved to POST or 
  MODIFIED, depending on the product group. Bug reports can also return to
  this state if problems are found later in the work flow.

2.  https://bugzilla.redhat.com/page.cgi?id=fields.html doesn't show the mock-up that sgreen did at https://b.usersys.redhat.com/bug947139/ (which is currently unavailable).  His mock-up shows that CANTFIX is not a commonly used Resolution. Note that my changes to that text are minimal, and the insufficient info and can't reproduce cases text previously existed for CANTFIX.  I'm okay stripping it down to the following:

  CANTFIX
    The problem described is a bug report which cannot be fixed.  It may be
    a component which we do not support, or it has not received a reply 
    after requesting "needinfo" of someone for a while.  If possible, use
    more common resolutions such as WONTFIX or NOTABUG.  If must choose 
    this resolution, provide an explanation of why this resolution has been
    chosen in a comment.
Comment 4 Simon Green 2013-09-06 00:14:57 EDT
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon

Note You need to log in before you can comment on or make changes to this bug.