View Issue Details

IDProjectCategoryView StatusLast Update
0008392mantisbtfeaturepublic2012-10-22 15:54
Reporterafontquerni Assigned Todregad  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Summary0008392: Add another status "verified" or "tested" from point of view of testing
Description

Sometimes development phase and test phase are two steps.
Moreover developer and tester are diferents persons.

I think in several assigments to one issue (developer and tester [, and reporter]), permissions linked to status or to # issue.
In general, its improves roles and permissions.

TagsNo tags attached.

Activities

vboctor

vboctor

2007-09-24 10:38

manager   ~0015704

You can customize Mantis to use the statuses that match your process, please see the following article it the manual:

http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php

Let me know if this works for you.

afontquerni

afontquerni

2007-09-25 17:08

reporter   ~0015713

It is a great article.

Mainly, it resolves status needs. But...

  • Could I allow only testers to change issues into "verified" status ? (developers can't do it, but there are higher statuses for them)

  • Could I allow only an external project developer to access only one private issue ? (not all public issues for everybody and not all private issues for him)

  • Finally, we have two assignments for one issue: reporter and developer. But the reporter could not be the tester. And we would like to have filters to know who has tested the issue (the tester)

dregad

dregad

2012-10-10 13:30

developer   ~0033143

Could I allow only testers to change issues into "verified" status ? (developers can't do it, but there are higher statuses for them)

yes

Could I allow only an external project developer to access only one private issue ? (not all public issues for everybody and not all private issues for him)

This would be a challenge, not sure it can be done

Finally, we have two assignments for one issue: reporter and developer. But the reporter could not be the tester. And we would like to have filters to know who has tested the issue (the tester)

Not feasible, without using a e.g. custom field or a tag to store the tester's name