View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0012681mantisbtfeaturepublic2011-01-12 07:082019-02-03 11:00
Reportertk421 Assigned Tocproensa  
PriorityhighSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version1.2.4 
Summary0012681: Problem with "view all bug" page and all projects selected
Description

First of all, the configuracion is set that reporters can only see their own issues.

My user configuration is that i have some users with "developer" role in a determinate project, and these users are just "reporters" in all the other projects.

If one of these users access the "view issues" page, if there is a project selected, the user can see only his own issues if he is a reporter, and all issues if he is a developer. This is correct.

But if the "all projects" option is selected instead of a determinate project, user can see all issues in all project, even if in the projects he is just a reporter he can see other user's issues. I think this is a bug.

User can see issues in list, but if he tries to access an other user's issue, message "access denied" appears. This is correct, but i think the correct display of the list when "all project" is selected must hide issues of other reporters.

Additional Information

Sorry abotu my english, i hope you to underestand me and solve this issue.
Thank you very much

TagsNo tags attached.

Relationships

has duplicate 0012982 closedvboctor $g_limit_reporters has no effect. 

Activities

tk421

tk421

2011-05-18 14:03

reporter   ~0028798

I've found a partial solution that allows user view the issues in which user is reporter and also allows user to see issues that user has assigned

http://www.mantisbt.org/forums/viewtopic.php?p=44980#p44980
yw84ever

yw84ever

2011-05-23 05:12

reporter   ~0028816

Greetings. I myself am not sure how to set those settings, if through the web interface or if one need to manually enter the variables in the included php files:

http://docs.mantisbt.org/master/en/administration_guide.html#ADMIN.USER.ACCESS

From what you describe, the settings are correct and the behavior seen is indeed not what I would expect either.
cproensa

cproensa

2019-01-23 18:32

developer   ~0061288

This is probably fixed since filter improvements in v2.13