It's all about the answers!

Ask a question

How to move/copy custom work item types from one project area to other (or one server to other)


Akshay Panchakshari (37429) | asked Sep 16 '16, 2:09 a.m.
I have create custom work item type and i want to move the same to another Project area which is on another server.
Generally, we copy the entire process configuration source xml from one PA to other PA. But this is not standard way and also there are errors sometimes for PAs having different project template (ex- from SDLC to Agile). Is there any way we can move/copy only the required Work item type ?

Thanks
Akshay P.

2 answers



permanent link
Dinesh Kumar B (4.1k413) | answered Sep 16 '16, 3:35 a.m.
JAZZ DEVELOPER
Hi Akshay,

Certain values to work item attributes are based on "id" (identifier's).  For example, what you see as a work item status is internally a workflow state identifier, that is part of the workflow associated with that work item type. 

If you do not have a state in the target process area with the same identifier, you copied/moved work item's state will be inconsistent.

Coming to your question, you do not have to copy the complete pa's config source, you can take only the work item related source to the target pa and paste it in the right place there.  A bit risky, so needs to be done with caution.

Following sections would be important:
                <type category="com.ibm.team.workitem.workItemType.task" icon="processattachment:/workitemtype/task.gif" id="task" name="Task">
                   ...
                </type>

                <customAttributes category="com.ibm.team.workitem.workItemType.task">
                   ...
                </customAttributes>               

                <workItemCategoryBinding workItemCategoryId="com.ibm.team.workitem.workItemType.task" workflowId="com.ibm.team.workitem.taskWorkflow"/>

                <workflowDefinition id="com.ibm.team.workitem.taskWorkflow">
                ...
                </workflowDefinition>


Also important would be the Operation Behavior - Preconditions and Follow up actions on that work item.


Links to other work items would also be an important aspect to look at, below post has a very good discussion that could help you :
https://jazz.net/forum/questions/134174/is-it-possible-to-move-workitems-from-one-project-area-on-server-a-to-another-project-area-on-server-b

hope this helps.

Dinesh

permanent link
Matt Muller (59813674) | answered Sep 16 '16, 3:14 a.m.

Akshay,

I'm not too familiar with V5 & 6 but I do not think this is possible as a function.

Copy WI from PA to PA is a difficult one: The only way I have do it "quicker" than just re-entering the configuration is to Copy and Paste sections for the WI from in the Process Configuration XML.

The first time you do this it will take you a while  (If you have good naming / literal ID's that will help).

When you get the hang of it - looking in the XML and when you understand the structure it becomes easier.

Exceptions to this copy / Paste XML:  "Attachments" used for work Item Icon and Workflow and Custom Scripts.


Comments
Ralph Schoon commented Sep 16 '16, 5:14 a.m. | edited Sep 16 '16, 5:14 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

The approaches using copy suggested by Matt and Dinesh can work. However make sure to understand the assumptions and make sure that objects referenced by the pieces you copy/paste are actually available. You can seriously damage the process configuration using copy paste and it might be safer to just use the usual UI to redefine what you need.

1. Consider process sharing as a potential solution
2. In the Eclipse Client on the Process Configuration Source tab you can see the history of your process XML (right click on the editor window) which you can use to compare the versions for changes and you can also use this to access a version to roll back to

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.