It's all about the answers!

Ask a question

Question in Editing work item Defect & Task

John Bryan Sazon (341823) | asked Jun 25 '13, 11:34 p.m.
edited Jun 25 '13, 11:36 p.m.

By default Task & Defect share the same work item category. Any attribute I add on the Task also applies on Defect and vice versa.

I would like to know if it is possible to, add some field on Task but it must not be available or must be hidden on Defect. If yes, how?


2 answers

permanent link
Indradri Basu (1.8k1514) | answered Jun 26 '13, 2:36 a.m.
Hi Brian, the word work item category is confusing me so I am not sure if I understand your question totally...
It is true that some built-in attributes appears in both the workitem types but if you create your own custom attributes they should only appear on the workitem type on which you created them.
For an example, on the eclipse client, under Types and attributes section, if I select Defect and create an attribute there and then if I move on to Task I can't see the attribute I created for Defect. The presentations for the respective workitem types also follow the same behavior. Did I answered your question ?

John Bryan Sazon commented Jun 26 '13, 2:59 a.m. | edited Jun 26 '13, 3:40 a.m.

Thanks for the concern!

Defect and Task work item share this the same category:

So any edit I apply to Defect, it also apply to Task and vice versa. Defect and Task are default work items on Rational Tools right?

Krzysztof Kaźmierczyk commented Jun 26 '13, 3:41 a.m.

Hi Bryan,
That is true. In RTC you have defects and tasks in each out of the box template.

permanent link
Geoffrey Clemm (30.1k33035) | answered Jun 26 '13, 11:31 a.m.
I assume you are referring to the Scrum Process Template?
In 4.0.3, each of the default work item types in the Scrum Process Template have their own category.   In particular, the category of the Task work item type is while the category of the Defect work item type is
In general, if two work item types have the same category, then as you observe, any change to that category (e.g. adding a new attribute) applies to all the work item types which share that category.
To break that sharing, I believe you will need to create a new work item type, give it its own category, and then you can modify the two work item types independently.   Unfortunately, that does require you to define all the editors and such for the new work item type, but a lot of the work item type properties can be "duplicated" from an existing property, so that hopefully will speed up the process a bit.   If you are feeling adventurous, you could try editing the Process Configuration Source xml directly (you can always revert back to the original xml if things go awry).

Your answer

Register or to post your answer.