View Issue Details

IDProjectCategoryView StatusLast Update
0023570mantisbtbugtrackerpublic2019-07-08 19:04
Reportercproensa Assigned Tocproensa  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0023570: Implement limit_reporters as a threshold

There are some issues with the limit_reporters option:

  • It's an on/off flag, so the behaviour is not very configurable.
  • The meaning of reporter, is based on the ability of a user to create issues, so it depends on report_bug_threshold for each project.
  • The access level that is not limited by this option is not well defined, when report_bug_threshold is an array threshold with gaps.

A more standard approach is to have an option representing a threshold, the meaning should be inverted though: "access levels that CAN view other reporters' issues"
Being a threshold, the behaviour is well defined and would use the standard access api conventions.
However, a disadvantage is that the dynamic "who is a reporter" discovery is lost, so if report_bug_threshold is modified for some project, this options should be modified accordingly.

There are related requests to have a limitation for users to view only issues assigned to him, which can be implemented in the same way as the "reporter" threshold limit.


TagsNo tags attached.


related to 0010831 acknowledged how can I allow user to view only the issue that assigned to them 


Issue History

Date Modified Username Field Change
2017-10-31 19:02 cproensa New Issue
2019-07-06 08:15 cproensa Relationship added related to 0010831
2019-07-08 19:04 cproensa Note Added: 0062368
2019-07-08 19:04 cproensa Assigned To => cproensa
2019-07-08 19:04 cproensa Status new => assigned