Deploying an out-of-the-box Work Item to a process spec
Is it possible to deploy an out-of-the-box Work Item from one process template into a project created from a different process template?
We have built a process specification from the ground up (not based on any of the out of the box process templates) and now want to add a Work Item from the Scrum template to the process spec.
Is this possible?
We have built a process specification from the ground up (not based on any of the out of the box process templates) and now want to add a Work Item from the Scrum template to the process spec.
Is this possible?
5 answers
Is it possible to deploy an out-of-the-box Work Item from one process template into a project created from a different process template?
We have built a process specification from the ground up (not based on any of the out of the box process templates) and now want to add a Work Item from the Scrum template to the process spec.
Is this possible?
Hello,
Did you mean copy the design of the work item from the OTB process template to your current project? I guess you could try copy the xml code for workitem from the process configuration source tab of the out of box template and paste them to source code of your current project. I have not tried that before so can't guarantee it will work, but worth a try.
Susan
Hi
Copying the XML is the only option. For every configuration point in the work items section of the process specification editor, you have an according process xml source element (configuratoin-data element) (e.g. with id com.ibm.team.workitem.configuration.workItemTypes for Types and Attributes),
When copying you should include:
- work item type (types & attributes)
- workflow
- editor presentations
- quick info presentations
- enumerations
- workflow binding
- editor binding
- approval trackings
- maybe predefined queries
Be aware that there must not be more than one configuration-data element with the same id, if an element already exists, you have to merge its content.
Be sure to add the icons for the work item types, the enumeration and the workflow elements with the same name (path), otherwise you will have dangling references to icons that may/will lead to unexpected errors.
Regards
Marcel
Jazz Work Item team
Copying the XML is the only option. For every configuration point in the work items section of the process specification editor, you have an according process xml source element (configuratoin-data element) (e.g. with id com.ibm.team.workitem.configuration.workItemTypes for Types and Attributes),
When copying you should include:
- work item type (types & attributes)
- workflow
- editor presentations
- quick info presentations
- enumerations
- workflow binding
- editor binding
- approval trackings
- maybe predefined queries
Be aware that there must not be more than one configuration-data element with the same id, if an element already exists, you have to merge its content.
Be sure to add the icons for the work item types, the enumeration and the workflow elements with the same name (path), otherwise you will have dangling references to icons that may/will lead to unexpected errors.
Regards
Marcel
Jazz Work Item team
Be sure to add the icons for the work item types, the enumeration and the workflow elements with the same name (path), otherwise you will have dangling references to icons that may/will lead to unexpected errors.
Regards
Marcel
Jazz Work Item team
Could you provide further guidance on this? Where are the icons located? How can they be deployed to the new template?
The icons are stored as 'Process Attachments' and can be seen either in the Enumeration/Work Item Type/Workflow editor on the Process Specification tab, or in a 'raw' form on the first tab of the project area editor, in the (initially collapsed) attachments section. As far as I know, there is no elegant way to copy attachments from one project to another. On the first tab you can save the attachments to the file system and in the enumeration/work item type/workflow editor of your custom template, you can then add them again (they will then get the correct path automatically if you saved them with the default name; adding icons from the workflow editor will prepend the 'workflow/' path automatically).
It looks as if you could save the icons only one-by-one, but you can add all corresponding icons together (e.g. all enumeration or worklfow icons).
Regards
Marcel
Jazz Work Item team
It looks as if you could save the icons only one-by-one, but you can add all corresponding icons together (e.g. all enumeration or worklfow icons).
Regards
Marcel
Jazz Work Item team