It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884

question asked: May 06 '11, 12:47 p.m.
question was seen: 4,831 times
last updated: May 06 '11, 12:47 p.m.

Related questions

Prevent work item type from being assigned erroneous value

0
Michael Forte (21●2●1) | asked May 06 '11, 12:47 p.m.
Is there a way in the process configuration to prevent a work time type (say a task) from being able to be assigned a complexity (points) which should be reserved (normally) for a story?

For example, if a CSV file contains import definitions for a work item type Story and work item type Task and the fields "Acceptance Test" and "Story Points" (which are custom attributes in our process configuration) are included as follows: 

Acceptance Test ... Estimate  Story Points ... Type

In order to...                8 pts            Story

                    1 hour                     Task


The task is imported with an erroneous blank Acceptance Test value and a null or zero Story Points value which appear on the custom tab and are visible from a plan view (Story Points only).

Interestingly, the story is not imported with an erroneous Estimate value. I suspect this might be the case due to the fact that Estimate is not a custom attribute.

Thanks!
Mike

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Kim Soederhamn (1.5k●3●43●48) | answered May 13 '11, 5:24 a.m.
Hey Mike,

Not entirely sure - but you could add the field and then setup validation for the field that way import would fail if the field contained something.

Also check out if your work items enherit this field from other work item types which may be the root cause to your problems.
0
permanent link
Michael Forte (21●2●1) | answered Jun 08 '11, 10:13 a.m.
Hey Mike,

Not entirely sure - but you could add the field and then setup validation for the field that way import would fail if the field contained something.

Also check out if your work items enherit this field from other work item types which may be the root cause to your problems.


Hi Kim,

Thanks for the tip. I actually ended up opening a defect for this issue. Currently in the RTC dev backlog. The ideal solution would be to allow control through the mapping file. Additionally, if a field is blank, then don't import it if it isn't a standard field for that defined type of work item.

Defect: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/167021

Related thread: https://jazz.net/forums/viewtopic.php?p=57612#57612

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.