-
Bug
-
Resolution: Fixed
-
High
-
3.13, 3.13.1
-
3.13
-
To reproduce this issue, you need to have two projects (A and B) and a user with a permission scheme with 'Resolved Issues' permission on project A, and on project B this permission is not granted.
In that case, the user can create an issue with a fix version in project A, and if he clones and moves this issue to project B, the cloned issue will have a fix version equal to its parent issue, even if this version is not existing in project B.
It should be better to remove the fix version during the move to avoid misunderstandings.
- is duplicated by
-
JRASERVER-16601 Moving an issue to another project keeps old project's fix version
- Closed
- relates to
-
JRASERVER-13011 Component of a subtask is still component of original project after moving an issue
- Closed