Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Bulk Move Issues from one project/component to another project/component

web-app

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
sgirolami
Replies (8)
helpful
0
not helpful

Could it be as easy as doing one of the following things:

A.  Move the component
Change [dbo].[geminicomponents].[projectid] from the old projectid to the new projectid.  This would essentially move all the issues in that project's component to my new project, then I can reassign the components from there.  But at least all the issues would be in the new project.

B.  Update the issue's assigned project and its component releationship.
Update [dbo].[gemini
issues].[projectid] from the old projectid to the new projectid.
Update [dbo].[gemini_issuecomponents].[componentid] from the the component in the old project to a component in the new project.

Unless I am missing something it looks like I can do either of those 2 things.  I don't have a database schema, so if there is anything I am missing please let me know. 

sg


sgirolami
· 1
sgirolami
helpful
0
not helpful

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.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

I figured that was the case.  I am downloading 3.1 now and will let you know what my results are.

By the way, I'd also like to say how much I like the new 3.x line of development.  I have read over the past couple months some harsh criticism regarding the hardship some are having with the added complexity of the "schemes" architecture, but I give it a thumbs up.  Most appreciated is the field visibility scheme.

My advice to others is to set up a second IIS site, and a second copy of your db to play with.  I gave myself 3-5 days to play with the new version, going through the database upgrade process a few times before I had a clean upgrade that I could depend on.  Getting intimate with schemes is critical if your migration is going to be well supported during the first couple weeks following a production upgrade, so do your homework.


sgirolami
· 1
sgirolami
helpful
0
not helpful

Appreciate the good feedback.

Thanks very much.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

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


mbedirian
· 1
mbedirian
helpful
0
not helpful

What issues are you having with "bulk move" and 3.5?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

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

 


Fanny
· 1
Fanny
helpful
0
not helpful

The bulk move page shows you target components to move to. So create the components in the target project and you should be fine.


Saar Cohen
· 5000
Saar Cohen