Assigning a distinct workflow to Defects
The Type Category com.ibm.team.workitem.workItemType is used for both Defects & Tasks in the Scrum Process template. This Type Category is bound to the Default Workflow.
As a Defect is a specialised WorkItem it warrants it s own specific workflow. E.G. Before working on a Defect it might be required that it always goes to triage state next; but this is not required for a Task.
E.G. After working on a Defect it might be required that it only goes to verify state next; but this is not required for a Task.
Is there a way to decouple Defect & Task from the Type Category com.ibm.team.workitem.workItemType so that separate workflows can be assigned to each?
As a Defect is a specialised WorkItem it warrants it s own specific workflow. E.G. Before working on a Defect it might be required that it always goes to triage state next; but this is not required for a Task.
E.G. After working on a Defect it might be required that it only goes to verify state next; but this is not required for a Task.
Is there a way to decouple Defect & Task from the Type Category com.ibm.team.workitem.workItemType so that separate workflows can be assigned to each?
8 answers
Hi,
you can always create a new work item category with a different workflow. You can create a new defect type for that category. Then you have different workflows for both categories. then you could remaove the old type. This would be ideally done for a new project e.g. create a desired project template you want to use.
In an existing project there might be issues. You could move all existing defect work items to the new work flow by changig to the new type.
I'd expect potential issues with the existing workflow states though.
Hope this helps,
Ralph
you can always create a new work item category with a different workflow. You can create a new defect type for that category. Then you have different workflows for both categories. then you could remaove the old type. This would be ideally done for a new project e.g. create a desired project template you want to use.
In an existing project there might be issues. You could move all existing defect work items to the new work flow by changig to the new type.
I'd expect potential issues with the existing workflow states though.
Hope this helps,
Ralph
The Type Category com.ibm.team.workitem.workItemType is used for both Defects & Tasks in the Scrum Process template. This Type Category is bound to the Default Workflow.
As a Defect is a specialised WorkItem it warrants it s own specific workflow. E.G. Before working on a Defect it might be required that it always goes to triage state next; but this is not required for a Task.
E.G. After working on a Defect it might be required that it only goes to verify state next; but this is not required for a Task.
Is there a way to decouple Defect & Task from the Type Category com.ibm.team.workitem.workItemType so that separate workflows can be assigned to each?
Hi
It is possible to move a type into a different type category and even bind to a different workflow without getting inconsitent regarding the data in the repository. However you have to be very careful when doing this.
I decided to write the steps down in task work items (to be converted into a FAQ eventually) for better maintainability:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/97139 and
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/97138.
Regards
Marcel
Jazz Work Item team
It is possible to move a type into a different type category and even bind to a different workflow without getting inconsitent regarding the data in the repository. However you have to be very careful when doing this.
I decided to write the steps down in task work items (to be converted into a FAQ eventually) for better maintainability:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/97139 and
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/97138.
Regards
Marcel
Jazz Work Item team
Hi
I do not expect this split to become a feature of RTC as all the newer process templates only contain one work item type in a type category. The 'split' is mainly needed for project areas created with RTC 1.0 and before.
The type category concept exists for historical reasons and will eventually be removed (item 72855: Consider to get rid of the type category https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/72855), however I don't think that this will happen soon.
Regards
Marcel
Jazz Work Item team
I do not expect this split to become a feature of RTC as all the newer process templates only contain one work item type in a type category. The 'split' is mainly needed for project areas created with RTC 1.0 and before.
The type category concept exists for historical reasons and will eventually be removed (item 72855: Consider to get rid of the type category https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/72855), however I don't think that this will happen soon.
Regards
Marcel
Jazz Work Item team
We are using RTC 2.0 & even newly created Projects with Agile / Scrum process templates have items still combined.
Hi
I do not expect this split to become a feature of RTC as all the newer process templates only contain one work item type in a type category. The 'split' is mainly needed for project areas created with RTC 1.0 and before.
The type category concept exists for historical reasons and will eventually be removed (item 72855: Consider to get rid of the type category https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/72855), however I don't think that this will happen soon.
Regards
Marcel
Jazz Work Item team
Did you upgrade from RTC 1.0 or 1.0.1.1 to RTC 2.0? If so, it sounds like your repository may still contain the older templates. This link will tell you how to deploy the latest versions of the templates:
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390870
Note that the Agile template was not included with RTC 2.0, so work items and defects will continue to be combined.
Martha
http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390870
Note that the Agile template was not included with RTC 2.0, so work items and defects will continue to be combined.
Martha
We are using RTC 2.0 & even newly created Projects with Agile / Scrum process templates have items still combined.
Hi
I do not expect this split to become a feature of RTC as all the newer process templates only contain one work item type in a type category. The 'split' is mainly needed for project areas created with RTC 1.0 and before.
The type category concept exists for historical reasons and will eventually be removed (item 72855: Consider to get rid of the type category https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/72855), however I don't think that this will happen soon.
Regards
Marcel
Jazz Work Item team
The direct link for the redeploy is:
http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21390698.
Regards
Marcel
Jazz Work Item team
http://www-01.ibm.com/support/docview.wss?rs=0&uid=swg21390698.
Regards
Marcel
Jazz Work Item team
I was looking for the default work flow of defect, Task, Story, Feature etc required
Work flow should describe like
New Defect created with Status = New
From New status can be changed from New to In Process etc.
And the document describing the rights i.e. which user can change which status. Like Senior Developer created the defect. Junior Developer can change the status from In Progress to Resolve but cannot change the status of Verify or Close etc.
Work flow should describe like
New Defect created with Status = New
From New status can be changed from New to In Process etc.
And the document describing the rights i.e. which user can change which status. Like Senior Developer created the defect. Junior Developer can change the status from In Progress to Resolve but cannot change the status of Verify or Close etc.