I can't reproduce this here. Can you reproduce it on this installation?

No i can't. Maybe that is because i'm a reporter only - not a manager like in my mantis. Have a look at the attached screenshot after chosen a specific project. Pay attention at the box containing "Assigned to Me (Unresolved)" which i don't get here.

edited on: 08-31-04 08:28

The behaviour resulted of different roles in different projects.
E.g. i'm a manager in one project and reporter in another.

I changed the following config and the requested feature now works for me:

$g_handle_bug_threshold = REPORTER;
(access level needed to be able to be listed in the assign to field.)

(which was set to DEVELOPER before)

You could define this issue as resolved now or discuss to change the behaviour to show issues from all projects where i'm in the given role (DEVELOPER) or higher which makes sence for me.

Yeah, that makes more sense.

To confirm:

• "Assigned to Me" is not displayed to users that bugs can't be assigned to (through handle_bug_threshold)
• "Monitored by Me" is not displayed to users that can't monitor bugs (through monitor_bug_threshold)
• "Reported by Me" is not displayed to users that can't report bugs (through report_bug_threshold)
• All other boxes are displayed to all users

The actual checking is done in the same way as per the other parts of Mantis - ie. in the Least Common Denominator fashion.

For example, Report Issue is sometimes not visible in All Projects even if a user has Reporter level on some projects but not on others.

I ran into effectively the same problem in the View Issues page.
My global default access is VIEWER, however, for all of the projects in our installation I have a higher level of access.

But when I am in "All Project" view it uses the global default access of VIEWER

I also could not use a filter that had "[MYSELF]" in the handler field when I was viewing all projects.

I think at the very least the access level for ALL PROJECTS should be the lowest level of access you have in all projects (which in my case is higher than the default access).

I don't think that that is necessarily the best solution either. Even if I am not a report in one of the projects I would still like the have the report issue link when viewing all projects.

Is this issue considered fixed (due to config conflict), or is there work that sould be done to resolve the issue of having a user be a reporter in one project and a developer in another?

No, I think this needs to be addressed still.

I think the my view page should provide a global overview of all issues related to the user.

Selecting "All projects" should show ALL issues assigned to, reported by, ... the user, independant of the "Least Common Denominator".
Otherwise if in one project all users (except admin) are viewers, they can't get an overview of all projects.
I think it is not (or less) relevant whether each of the 6 sections are visible or not.

Perhaps in a a perfect world this would be configurable. Users should be able to choose what boxes are shown for projects where they are developers or reporters (or not even logged in as a site wide setting).

However, as a default setting I think the way it is now is just fine.

Customizable "My View" page is tracked in 0007840