View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0023208||mantisbt||bugtracker||public||2017-08-10 12:38||2017-12-05 05:48|
|Summary||0023208: Threshold for setting fields such as priority|
Many end-users do not really understand what issue priority is (or how we use it). For example, if they find that an issue is important to them, they might set the priority to "immediate". Quite often this does not reflect the reality and it would make more sense that only users above a certain threshold could set the priority (or other fields such as severity). Typically it is the developer who decides what an issue's priority should be.
By looking through the default config variables, I figured that I can completely remove this field but there is no way to set some sort of edit threshold for this and other fields. It would be great if there was a threshold for editing certain fields.
|Tags||No tags attached.|
In my configuration, I have priority hidden when reporting, and rporter users cant go into the edit page.
The core issue is that native fields can't have a detailed configuration for each one, like custom fields have. Ideally, all field types should be configurable for where to be shown, where to be required, who can view/update them, etc. But that's not an easy change at the moment.
I agree that doing it through options is probably not the optimal way (per-project configurations or similar could be better).
I have done something similar in that scenario, so i'm sure that would work in some way.
Another option, but dirtier imo:
|2017-08-10 12:38||j_schultz||New Issue|
|2017-08-10 15:42||atrol||Relationship added||has duplicate 0017005|
|2017-08-10 15:42||atrol||Severity||minor => feature|
|2017-08-11 04:28||cproensa||Note Added: 0057431|
|2017-08-11 07:29||j_schultz||Note Added: 0057436|
|2017-08-11 08:00||cproensa||Note Added: 0057437|
|2017-08-11 08:06||cproensa||Note Edited: 0057437||View Revisions|
|2017-12-05 05:48||atrol||Relationship added||has duplicate 0023697|