This question is locked. New answers and comments are not allowed.
Hi
We are currently testing Team Pulse as a tool to consolidate our development environment with Support and business users.
Everything is working fine, except that it would be great if we could move stories between projects.
Scenario:
1. Callcentre receives a call and logs the call on their project using Team Pulse
2. Call gets investigated and is identified as a bug, Story is converted to a bug or new bug is created in the system and linked to the issue.
3. Once the issue has been identified as a bug, it needs to be moved to the relevant project for the developers, but still needs to be linked to the originating issue.
4. This also sometimes happens on development: Multiple projects have integration points, causing ideas to be relative to multiple projects. Stories can thus span multiple projects in these scenarios.
Being able to move stories between projects and have tasks within them in different projects would be a great help.
Regards
We are currently testing Team Pulse as a tool to consolidate our development environment with Support and business users.
Everything is working fine, except that it would be great if we could move stories between projects.
Scenario:
1. Callcentre receives a call and logs the call on their project using Team Pulse
2. Call gets investigated and is identified as a bug, Story is converted to a bug or new bug is created in the system and linked to the issue.
3. Once the issue has been identified as a bug, it needs to be moved to the relevant project for the developers, but still needs to be linked to the originating issue.
4. This also sometimes happens on development: Multiple projects have integration points, causing ideas to be relative to multiple projects. Stories can thus span multiple projects in these scenarios.
Being able to move stories between projects and have tasks within them in different projects would be a great help.
Regards
3 Answers, 1 is accepted
0
Hello Paul,
Elena Peneva
the Telerik team
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
Thank you for contacting us and sharing your feedback.
Our team has received similar feature requests before, so we created a feature request item visible on our feedback portal where people can vote and share their comments. I highly encourage you to open the link and vote for the item, as this will raise its popularity.
Here is another feature request from our client that might interest you - Cross Project Story Linking.
Feel free to use our Feedback portal for sharing your ideas and voting on features that will help TeamPulse suit your needs best.
Elena Peneva
the Telerik team
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
0
Exchange
Top achievements
Rank 1
Rank 1
answered on 29 Apr 2014, 09:17 PM
Its seems this request has been there for nearly 3 years. Is there any idea on when/if this request will ever get worked on? If not, are there other ways we could move a story from one project to another. Are there database queries we could use to accomplish this?
0
Hello,
The problem that we are facing is that in some projects you could have different fields, that are not allowed in your new project. So if you move a story, it won't have the allowed values for the new project.
You could move your story with an sql query, by simply changing the projectID, areaID and iterationID fields in dbo.WorkItem table. If you have any values that are different in your target project, you could also change them with a query (for example status field).
Note that this will work only for stories without relationships, tasks, attachments, acceptance criteria and so on.
If you want to move a story (or other workitem type) with all it's data you could use the attached script.
Note that on row 17 is the select statement. Now the script will only move your Feedback items.
Also on row 164 there are several things that you need to change:
Declare your projectIDs here:
DECLARE @oldProjectIDtoMigrate INT = 1;
DECLARE @newProjectIDtoMigtare INT = 2;
and also declare your new project area id (all items will be moved to one area)
DECLARE @newProjectAreaID INT = 1;
Please, before doing this on your live database be sure it's tested and working on test environment, because this might change the data in your project that you don't want to.
If you need further assistance, feel free to contact us at any time.
Regards,
Ivan
Telerik
The problem that we are facing is that in some projects you could have different fields, that are not allowed in your new project. So if you move a story, it won't have the allowed values for the new project.
You could move your story with an sql query, by simply changing the projectID, areaID and iterationID fields in dbo.WorkItem table. If you have any values that are different in your target project, you could also change them with a query (for example status field).
Note that this will work only for stories without relationships, tasks, attachments, acceptance criteria and so on.
If you want to move a story (or other workitem type) with all it's data you could use the attached script.
Note that on row 17 is the select statement. Now the script will only move your Feedback items.
Also on row 164 there are several things that you need to change:
Declare your projectIDs here:
DECLARE @oldProjectIDtoMigrate INT = 1;
DECLARE @newProjectIDtoMigtare INT = 2;
and also declare your new project area id (all items will be moved to one area)
DECLARE @newProjectAreaID INT = 1;
Please, before doing this on your live database be sure it's tested and working on test environment, because this might change the data in your project that you don't want to.
If you need further assistance, feel free to contact us at any time.
Regards,
Ivan
Telerik
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.