It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884

question asked: Nov 14 '08, 12:29 p.m.
question was seen: 6,380 times
last updated: Nov 18 '14, 8:10 a.m.

Related questions

Moving Tasks & Stories between different projects

0
Behzad Salami (21●2●2) | asked Nov 14 '08, 12:29 p.m.
Has anyone been successful in moving tasks or stories from one RTC workspace to another ?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Nov 16 '08, 2:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I assume you meant "move task/story from on RTC project area to another"?

If so, have you tried the "Move/Copy to Project Area..." operation on a
workitem?

Cheers,
Geoff

bsalami wrote:
Has anyone been successful in moving tasks or stories from one RTC
workspace to another ?
Comments
Sedat kara commented Nov 17 '14, 6:30 a.m.

Hi Geoffrey, 

"Move/Copy to Project Are" it working. Is there any way to do from the work item editor ? For example making " Project Area: field in workitem editor modifiable with an enumeration from which we can choose the project. 

PS: My question on this topic : https://jazz.net/forum/questions/167903/moving-a-task-from-a-plan-to-another-with-different-workflow
 

sam detweiler commented Nov 17 '14, 7:24 a.m.

the only straight forward way is for you to create a new attribute, which is a dropdown list of projects, and then create a participant to move the workitem to the appropriate project.

Sedat kara commented Nov 17 '14, 10:02 a.m.

Thanks Sam, 


We will end up to realize this project together :). 
I understand very well your proposl up to "a dropdown list of projects" but I need more details for the second part please. What do you mean with "create a participant to move the workitem to the appropriate project" :)

Thanks a lot,

sam detweiler commented Nov 17 '14, 2:32 p.m.

there is the ability to extend the server side operations

1. advisor
      this does checking and could stop a save if there is invalid data or something
      cannot change data
2. participant (executed AFTER the save) ,
      can change the data in the workitem and save it AGAIN

see the workshops
https://jazz.net/library/article/1000
and
https://rsjazz.wordpress.com/2014/06/11/running-rtc-4-x-extensions-workshop-with-rtc-5-0/

net, you would add a new enumeration to each workitem, which has the list of projects, and then u would select a different entry.. on save., the participant would then do whatever is needed to move the workitem to the other project, selected in the dropdown.  (I don't know all things that have to be done to accomplish the move)..

I am really against this approach.. the multiple unique tasks and you get 'part' of your kanban board view. The tasks will be there, but the actual state will not be in the board column header

Sedat kara commented Nov 18 '14, 8:10 a.m.

thanks for your explanation. 

I will realy take into consideration your advice to not opt for this approach. I would like to have this way to do in the very last case. 

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.