-
Suggestion
-
Resolution: Duplicate
-
None
Moving an issue between projects preserves the status of the orginating issue.
The status is (and should be) controlled by the project's workflow.
Even if the workflows are the same between the projects, the people allowed to perform the transitions not.
The result is that the moved issue circumvents the workflow and team responsible for approving/transitioning the issue. Issues are often lost, because they don't enter the workflow at the beginning.
The Moved issue should retain all the data from the orginal issue, but start in whatever the status the workflow sets as the "created" status.
This is related to JRA-5159
- duplicates
-
JRASERVER-1558 Deep copy an issue to the same project or a single project
- Gathering Interest