View Issue Details

IDProjectCategoryView StatusLast Update
0011005mantisbtfeaturepublic2010-04-23 23:22
Reporterwatergad Assigned Tovboctor  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionduplicate 
Product Version1.2.0rc1 
Summary0011005: Configurable access to "Priority" field
Description

It would be nice to have Priority field access configurable.
Customers may want to set priority when reporting bugs.

Now I changed bug_report_advanced_page.php:

if ( access_has_project_level( config_get( 'handle_bug_threshold' ) ) ) {
to
if ( access_has_project_level( config_get( 'report_bug_threshold' ) ) ) {

but I feel like I fall to the dark side this way (:

TagsNo tags attached.

Relationships

duplicate of 0010728 closedvboctor Refactor reporting page to allow controlling which fields should be visible 

Activities

thraxisp

thraxisp

2009-10-05 14:58

reporter   ~0023067

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.

watergad

watergad

2009-10-05 15:25

reporter   ~0023068

Agreed, that's how this field is supposed to be.
But sometimes we have to show that the problem is not so important but must be done quick.
And we're not so vulnerable because customers make reports through competent IT department.

Just it's useful in some cases - but ok, I agree, not so often.

dhx

dhx

2009-10-06 05:36

reporter   ~0023077

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.

watergad

watergad

2009-10-19 06:36

reporter   ~0023236

Done in 1.2.0rc2

vboctor

vboctor

2009-10-19 16:53

manager   ~0023247

@watergad, can you provide the issue number that included the work you were asking for here?