Contributing states for a new work item type

Basically, I'm trying to contribute a work item into Jazz similar to
'Plan' or 'RFS' where it's a work item that's accessible from the same
interface as a 'Defect' or a 'Task' but they have their own unique
states that aren't the same as what's shown in the bugzillaWorkflow.xml
contained within the com.ibm.team.workitem.service plug-in.

Regards,
Rem

Remy Chi Jian Suen wrote:

Basically, I'm trying to contribute a work item into Jazz similar to
'Plan' or 'RFS' where it's a work item that's accessible from the same
interface as a 'Defect' or a 'Task' but they have their own unique
states that aren't the same as what's shown in the bugzillaWorkflow.xml
contained within the com.ibm.team.workitem.service plug-in.

There are two more things to do (besides defining an own type). Declare
a workflow and bind the workflow to the respective workitemCategory.
For the binding to work your contributed type has to have its own
workitemCategory. RFS and Plan item can be taken as example for the
workflow and the binding.
If defining a workflow is not self-explanatory enough, don't hesitate to
ask.

Marcel

Marcel Bihr wrote:

For the binding to work your contributed type has to have its own
workitemCategory. RFS and Plan item can be taken as example for the
workflow and the binding.

If I define my own category, I do not appear to see it in the drop down
list when I create a new work item, I only see the original five.

If I set the category "com.ibm.team.workitem.workItemType", then it just
uses the bugzilla workflow.


<extension
point="com.ibm.team.workitem.service.workflowDescription">
<workflowDescription class="com.abc.whatever.MyWorkflow"
id="myWorkflow"
name="My Workflow">
</workflowDescription>
</extension>
<extension
point="com.ibm.team.workitem.service.workflowBinding">
<workItemCategoryBinding
workItemCategoryId="myWorkItemType"
workflowId="myWorkflow">
</workItemCategoryBinding>
</extension>
<extension point="com.ibm.team.workitem.common.workItemType">
<workItemType id="myWorkItemId"
category="myWorkItemType"
name="My Work Item"
icon="icons/wi_task.gif" dimmedicon="icons/wi_task_dim.gif" />
</extension>

Regards,
Rem

Creating a new WorkItem category that starts with
"com.ibm.team.workitem.workItemType" does the trick,
e.g "com.ibm.team.workitem.workItemType.myCategry"

Right now we only show WorkItem types in the drop down list that are in
the same category, or in a "subcategory" (where subcategory means: an
extensions of the base categories string).

We will fix this in the future.

--andre

On 2007-07-12 14:09:36 +0200, Remy Chi Jian Suen <remsuen@ca.ibm.com> said:

Marcel Bihr wrote:
For the binding to work your contributed type has to have its own
workitemCategory. RFS and Plan item can be taken as example for the
workflow and the binding.

If I define my own category, I do not appear to see it in the drop down
list when I create a new work item, I only see the original five.

If I set the category "com.ibm.team.workitem.workItemType", then it
just uses the bugzilla workflow.


extension
point="com.ibm.team.workitem.service.workflowDescription"
workflowDescription class="com.abc.whatever.MyWorkflow"
id="myWorkflow"
name="My Workflow"
/workflowDescription
/extension
extension
point="com.ibm.team.workitem.service.workflowBinding"
workItemCategoryBinding
workItemCategoryId="myWorkItemType"
workflowId="myWorkflow"
/workItemCategoryBinding
/extension
extension point="com.ibm.team.workitem.common.workItemType"
<workItemType id="myWorkItemId"
category="myWorkItemType"
name="My Work Item"
icon="icons/wi_task.gif" dimmedicon="icons/wi_task_dim.gif" /
/extension

Regards,
Rem

Hi,

Using a prefix of 'com.ibm.team.workitem.workItemType' did allow my work
item to show up, but it is still not using my custom workflow.

<extension
point="com.ibm.team.workitem.service.workflowDescription">
<workflowDescription
class="com.ibm.test.TestWorkflow"
id="myWorkflow"
name="Test Workflow">
</workflowDescription>
</extension>
<extension
point="com.ibm.team.workitem.service.workflowBinding">
<workItemCategoryBinding
workItemCategoryId="com.ibm.team.workitem.workItemType.myCategory"
workflowId="myWorkflow" />
</extension>
<extension point="com.ibm.team.workitem.common.workItemType">
<workItemType id="test"
category="com.ibm.team.workitem.workItemType.myCategory"
name="Test Work Item"
icon="icons/wi_task.gif" dimmedicon="icons/wi_task_dim.gif" />
</extension>

I have been unable to find the exact xml extension point declarations
for the Plan Item and RFS work items. Could someone tell me where
they're at or can paste it here in a newsgroup post? I am using 0.6M1.

Thanks,
Rem

Andre Weinand wrote:

Creating a new WorkItem category that starts with
"com.ibm.team.workitem.workItemType" does the trick,
e.g "com.ibm.team.workitem.workItemType.myCategry"

Right now we only show WorkItem types in the drop down list that are in
the same category, or in a "subcategory" (where subcategory means: an
extensions of the base categories string).

We will fix this in the future.

--andre

On 2007-07-12 14:09:36 +0200, Remy Chi Jian Suen <remsuen@ca.ibm.com> said:

Marcel Bihr wrote:
For the binding to work your contributed type has to have its own
workitemCategory. RFS and Plan item can be taken as example for the
workflow and the binding.

If I define my own category, I do not appear to see it in the drop
down list when I create a new work item, I only see the original five.

If I set the category "com.ibm.team.workitem.workItemType", then it
just uses the bugzilla workflow.


extension
point="com.ibm.team.workitem.service.workflowDescription"
workflowDescription class="com.abc.whatever.MyWorkflow"
id="myWorkflow"
name="My Workflow"
/workflowDescription
/extension
extension
point="com.ibm.team.workitem.service.workflowBinding"
workItemCategoryBinding
workItemCategoryId="myWorkItemType"
workflowId="myWorkflow"
/workItemCategoryBinding
/extension
extension point="com.ibm.team.workitem.common.workItemType"
workItemType id="myWorkItemId"
category="myWorkItemType"
name="My Work Item"
icon="icons/wi_task.gif"
dimmedicon="icons/wi_task_dim.gif" /
/extension

Regards,
Rem

I've managed to get it working now. Not sure what I did differently, but
whatever. :)

Thanks all.

Regards,
Rem