User's priviledge and bug fix verification process

[bugview08]

Hello everyone:

I am learing to use Mantis. I have several questions and hope you ca help me to find the solutions.

1. Assign user multiple access level .
I currently assign the user different access level by using the same email address to create different accounts (e.g. reporter,
administrator, develper etc)

I am wondering if I can give a single user multiple roles at one time, instead of creating serveral accounts with same email address.
Should I customize certain file to make this happen?

2. Can reporter close a bug after verification?

Once bug status is resolved(fixed) only manager level user can close the bug, regular reporter can't.

Can I modify the reporter's access level to handle_bug_threshold or higher ?
http://manual.mantisbt.org/manual.page. ... .to.me.php this link showed if user have access level
to "handle_bug_threshold or higher", they can close the bug. Please advise how can I make it work.

2a. Developer and Administrator can not assign a bug to reporter for verfication purpose.
I log in as admin or developer, then I try to assign bug to reporter, is 'Assign to' drop down box, there was no reporter.
what kind of customization I should do so reporter and developer can assign bug directly to reporter?

3. which table in database stored information about bug status.
3a.which table(s) are queried to display information on Issue History section.

4. Customize Search feature:
for default setting, user can search bug by issue#.
If I want to customize the search so user can search bug by project name, sub-project name etc,which files should I customize?

5. How monitor feature works in Mantis?

Please give me some suggestion and related the links for my questions. I appreciate your help!

[jb_mantis]

1. I don't believe multiple access levels are currently an option. Remember that, in general, higher levels inherit the permissions of the lower levels. That is, in general, a developer can do anything that a view, reporter or updater can do. You should be able to give a user a single access level and edit that level's permissions through other configuration options to achieve the desired abilities.

2. This can be set by this option "Manage Configuration -> Workflow Thresholds -> Allow Reporter to close Issue" (in Mantis 1.1.2).
2a. This can be set by this option "Manage Configuration -> Workflow Thresholds -> Handle an issue" (check the box for Reporter).

3. Don't know. I don't mess with the tables.

4. Don't know. I can't imagine an environment with so many projects and subprojects that you have to search them to find the one you want.

5. A user that is monitoring an issue will receive a copy of the email notifications that the reporter receives. See link below.
http://www.mantisbt.org/manual/manual.p ... or.bug.php

[olegos]

I've been thinking that there should be a state Verified between Resolved and Closed. I will probably add it in my installation by following instructions here.

Is it possible to make Resolved -> Verified transition available only to Developers and above, and the original Reporter (but not other reporters)?

[bugview08]

Hello Joe:

Thanks for your help! I got my questions solved:)

[jb_mantis]

Olegos,
I don't think so. There is an option that allows reporter's to close their own issues but I am not sure that would apply to a custom state created before it. Why do you think you need a state between Resolved and Closed? What situation is it meant to handle? Once a developer has either fixed or justifiably not-fixed an issue, they should mark it Resolved. Once the Reporter or Manager agrees with their resolution, it should then be closed. If the Reporter does not agree, it should be reopened and feedback given. I can't think of anything that could happen besides agreeing with the Resolution and closing the issue or disagreeing and reopening it.

[olegos]

In my configuration issues don't become read-only until Closed. I don't like closing issues right after they get resolved -- that drops them off of the default filter that many people use, and I want people to have a chance to read the resolution, and comment on it if they want. So I ask my users not to close issues in less than a week after Resolved. I'm considering only letting managers close issues. I think it makes sense for managers to only close issues that are in Verified state, and have been there for more than a week, if everything looks good.