Changing the Project of a Ticket
|
|
Is there a way to change the project that a ticket is assigned to? We’ve currently got about 150 tickets in a holding area that need to be assigned to individual projects, but I don’t see an option to move them. |
|
|
Bill, There is not currently a facility within Unfuddle to migrate tickets from one project to another. Said differently. we did not anticipate that our customers would be using intermediate projects as ticket staging areas—this was simply never one of our original use cases. That being said, we are considering adding this ability in response to feedback such as yours. In the interim, I would suggest: 1) not using an intermediate staging project for any new tickets; 2) manually moving these tickets into their appropriate projects; and or 3) writing what would be a small script against the Unfuddle API that would migrate tickets from one project to another. |
|
|
I would also find this functionality very useful (bordering on required). We don’t use a staging area; however, we do have multiple projects that are related. It is not uncommon for someone to put a bug or feature request into the wrong project. Moving it to another project is very cumbersome at the moment… I realize that we could make one project and then use the Component fields; however, that wouldn’t provide the amount of granularity we need for time reports, milestones, etc (we are a medium size development team – about 15-20 developers with other entering bugs, feature requests, etc). Thanks, |
|
|
I believe this was recently implemented. |
|
|
I can confirm it’s possible to move around tickets… |
