Bulk Move Issues from one project/component to another project/component
I would like to bulk move issues from one project/component to another project/component.
I have access to the database and without affecting integrity, I want to just update ids so that issues assigned to "Project One"/"Component Three" will be moved to "Project Two"/Component One" or something like that.
Anyone got any thoughts. I want to acheive the result of moving a single issue, but perform that action against multiple issues at once. I do not want to disturb the comment history or any other foreign key data.
sg
sgirolami
· 1 |
|
Monday, December 15, 2008, 7:29:35 PM |
0
|
Could it be as easy as doing one of the following things: |
||||
|
0
|
Unfortunately, it is not that simple. The project id is stored in several places (for optimisation reasons). So you will have to update several tables (comments, history etc...) and make sure that the version(s) is correct. In 3.1 (beta is out) there is a bulk move option. |
||||
|
0
|
I figured that was the case. I am downloading 3.1 now and will let you know what my results are. |
||||
|
0
|
Appreciate the good feedback. Thanks very much. |
||||
|
0
|
Hi we are using Gemeni version 3.5 and I would like to know if the bulk-move issue has been resolved? I am trying to move issues from one project to another along with its components. Is there a workaround in the mean time?
Mireille |
||||
|
0
|
What issues are you having with "bulk move" and 3.5? |
||||
|
0
|
Bulk move allows users to move issues from one project to another. The problem is that the component where issues are created does not move with its issues. We are using Gemini 3.5. Is there a way around?
Thank you
|
||||
|
0
|
The bulk move page shows you target components to move to. So create the components in the target project and you should be fine. |
||||
|