View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011005 | mantisbt | feature | public | 2009-10-05 13:41 | 2010-04-23 23:22 |
Reporter | watergad | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | duplicate | ||
Product Version | 1.2.0rc1 | ||||
Summary | 0011005: Configurable access to "Priority" field | ||||
Description | It would be nice to have Priority field access configurable. Now I changed bug_report_advanced_page.php: if ( access_has_project_level( config_get( 'handle_bug_threshold' ) ) ) { but I feel like I fall to the dark side this way (: | ||||
Tags | No tags attached. | ||||
IMHO, this may not be wise. There are two fields: severity and priority. In practice, the severity field is set by the originator, and the priority field would be set by the developer after reviewing the bug and other circumstances. It would reflect the DEVELOPER'S priority in addressing the bug. If my reporters set this, their individual bugs would always be set to the highest priority, and the field would be useless. I'd rather see the field hidden from reporters. |
|
Agreed, that's how this field is supposed to be. Just it's useful in some cases - but ok, I agree, not so often. |
|
FYI I want to make built-in fields to share functionality/code with the custom field API. This would allow you to set the read/write access thresholds to the priority, severity, etc fields independently of each other. |
|
Done in 1.2.0rc2 |
|
@watergad, can you provide the issue number that included the work you were asking for here? |
|