Filtering the issue status based on user level??

[HomesicK]

hi all,

How to specify the issues status according to the user access level
(example: new & closed statuses must appear for the reporter & must not appear for the developer).

[HomesicK]

UP !

[atrol]

... new & closed statuses must appear ...

Are you talking about issues with this statuses or dropdown lists with statuses?

[HomesicK]

thanx my friend for your reply,,

I mean the dropdown lists with statuses

[atrol]

Aah, I remember ....
You are the one who does not trust his developers.
Seems that you also don't trust your reporters or anyone else.

See "Manage" -> "Manage Configuration" -> "Workflow Transitions" what can be done with standard MantisBT functionality.
At the bottom of this page you find "Minimum Access Level to Change to this Status"
If you want more than this (excluding higher access levels like developers from setting status) you will have to ask a developer to change source code.
As you don't trust any developer you have to fear that he will change the source code in a way that it seems for you that he can not change the status.
Be aware that he will be able to change the status if he wants.

[HomesicK]

Hi My friend ,,

I don't trust any body even me lol ,, am joking,, look my friend I will tell you the story :

I have a team consists of a team leader, developers, QA resourses (reporters). I want the reporters to have higher access level than the developers since the reporters are the ones who mainly use the system to report bugs. And based in your clarification below, the developer has higher access level class than the reporter!!.Now, Could I change the access levels for the reporter and developer to make the reporter (QA) has a higher level, or should I give my QA resources manager access level to solve this issue ??

[atrol]

or should I give my QA resources manager access level to solve this issue ??

This is the way I use MantisBT for internal projects/teams. QA users have DEVELOPER access level. QA is just one part of development. I use the REPORTER access level for external customers.

[HomesicK]

or should I give my QA resources manager access level to solve this issue ??

This is the way I use MantisBT for internal projects/teams. QA users have DEVELOPER access level. QA is just one part of development. I use the REPORTER access level for external customers.

That what I did already

Thanks for your cooperation my friend