View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020225 | mantisbt | documentation | public | 2015-10-26 21:04 | 2015-10-27 08:53 |
Reporter | cproensa | Assigned To | |||
Priority | none | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Summary | 0020225: $g_private_project_threshold as an array | ||||
Description | All through the code $g_private_project_threshold is treated as a mixed variable, of type integer, or array. What is the reason to use it as an array? By definition, i cant understand how that could work. Anyway, either documentation is wrong, or a lot of code is more complex than needed if its not an array in any case. | ||||
Tags | No tags attached. | ||||
The word threshold is confusing and does not express what the various threshold options mean. Goto page Manage > Manage Configuration > Permissions Report There can be more than one column checked, e.g. "viewer" and "administrator". Example of a use case that is not that synthetic: Typically the threshold to "Handle an issue" ($g_handle_bug_threshold) is DEVELOPER (which means DEVELOPER, MANAGER and ADMINISTRATOR can be assigned) |
|
I should have read the documentation before stressing my English ;-) From https://www.mantisbt.org/docs/master-1.2.x/en/administration_guide.html#ADMIN.USER.ACCESS Such threshold configuration options can be set to a single access level, which means users with such threshold and above are authorized to do such action. The other option is to specify an array of access level which indicates that users with the explicitly specific thresholds are allowed to do such actions. |
|
That is some ambiguity. At least i got it clear now. However, most of the comments supporting its usage in codebase are then misleading, as it says its type integer. |
|