[wp-trac] [WordPress Trac] #20041: Disable "Priority" and "Severity" fields for new users
WordPress Trac
wp-trac at lists.automattic.com
Sat Feb 18 18:59:54 UTC 2012
#20041: Disable "Priority" and "Severity" fields for new users
--------------------------------+----------------------------
Reporter: scribu | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: WordPress.org
Component: WordPress.org site | Version:
Severity: normal | Resolution:
Keywords: |
--------------------------------+----------------------------
Comment (by nacin):
The severity is the seriousness of the ticket in the eyes of the reporter.
The priority is the seriousness of the ticket in the eyes of the project.
Generally, severity is a judgment of how bad a bug is, while priority is
its relationship to other bugs.
We already disable priority, based particularly on this interpretation. I
think it's important to allow the reporter to reflect, at least initially,
how severe their bug is. For example, if data is lost due to the bug,
that's a major bug in terms of severity, at the very least. But if it's an
edge case, it may be a very low priority. And we might end up lowering
severity if we discover that it was was exacerbated by what the reporter
was trying to do.
Aside: To test what non-gardeners see, log in as `Scribu` in a separate
browsing window. Trac permissions are case-sensitive, so it won't think
you have special permissions beyond any other authenticated user.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/20041#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list