Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0012378 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [Mantis @ OB] Others | major | have not tried | 2010-02-22 12:18 | 2010-02-22 12:18 | |||||||
Reporter | plujan | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | urgent | Resolution | open | |||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | |||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Review Assigned To | ||||||||||||
Summary | 0012378: In my projects, user list for assigning issues is not correct | |||||||||||
Description | I have a project with five users. However, when I have to assign an issue, the user list has a least ten more users. Those users are "global", meaning that they are inherited, but they have no meaning in my workflows. | |||||||||||
Proposed Solution | I think users with global access should not be able to have assigned issue at least they were specifically added to the project. As example, I have no intention to assign an issue to hgbot user, nor Release Management team member (staffrm user included) nor managers. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Issue History | |||
Date Modified | Username | Field | Change |
2010-02-22 12:18 | plujan | New Issue |
Copyright © 2000 - 2009 MantisBT Group |