-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 2.6.1 Enterprise
-
Component/s: Project Administration - Permissions
-
Environment:
Tomcat 5.0.19, Suse Linux 8.2, j2sdk1.4.1_03, Sybase ASE 12.5
-
2.06
When moving an issue from one project to another the security level is not handled correctly.
a) The combo box shows the right number of entries, but except the first one ('None') these entries are empty. (The project where the issue belongs to has four different security levels, the project where the issue shall be moved to has no security level.)
b) If a security level has been selected 'blindly', the name of the security level is correct in the following form, but the label for the entry reads 'fixes version'.
After moving the issue, the security level is correct when selected 'blindly'.
- is duplicated by
-
JRASERVER-3641 Move Issues uses wrong security levels
-
- Closed
-