Ability to move issue between projects
This is similar to a previously posted question, but my request has nothing to do with status. We develop software that has a heavy content component. I would like to maintain separate projects for software and for content because they have different lifecycles and move through different people. But one of the objections raised to the idea of having a separate project for content is that if an issue is incorrectly reported in one project there is no easy way to move it into the other project.
Is there a way for a user to move issues between projects?
Celestine
· 1 |
|
Thursday, May 18, 2006, 12:23:28 AM |
0
|
You can move issues between projects by clicking the Move link when viewing the issue. Looks very simple and easy to me. |
||||
|
0
|
Thanks so much, Mark! I didn't even see that link. It is very simple. |
||||
|
0
|
I would like to move several hundred issues from one project to another, how can I do that?
|
||||
|
0
|
The best way to do this at the moment is by using Gemini web services. |
||||
|
0
|
Thank you for your quick reply. Can u pls provide further details on this. I ve never used a webservice before. |
||||
|
0
|
Sure, we have a sample app that demonstrates how to use Gemini services: http://www.countersoft.com/Default.aspx?PageID=58 download the Gemini Services Samples. |
||||
|
0
|
Sorry, but none of the downloadable files has any documentation nor an minimum readme, just dlls and some source code. I have totally no idea where and how to start. I not want to start learning programing webservices, just want to move some issues from one project to another. Isn't this possible with calling the stored procedure for moving the issue, which one is it, please provide the name and a sample.
Thanks in advance. |
||||
|
0
|
The stored procedure was drop as of 2.1, so if you are on 2.1.x or 2.2 there is no such stored procedure. |
||||
|