How to stop import default of Type = Defect?
If an import is done and there is anything wrong with the Type field, it still imports the row but sets Type = Defect. This not good. I then have to manually correct them all. I would prefer to get an error. I would like it to default to Unassigned but be a required field, thus it could not be saved with type set to Unassigned and would generate errors on import if Type was not properly assigned. Normally I could set the default under Enumerations and set it as a required field under Operation Behavior, but Type is in neither location. Any ideas?
5 answers
Hello,
searched jazz.net for similar feature - nothing found.
You may to open a new enhancement on jazz.net, against Work Item Component.
Thanks.
--
Eric JODET
Jazz Development - L3 Maintenance
Le 1/11/2011 2:38 AM, mshkolnik a crit :
searched jazz.net for similar feature - nothing found.
You may to open a new enhancement on jazz.net, against Work Item Component.
Thanks.
--
Eric JODET
Jazz Development - L3 Maintenance
Le 1/11/2011 2:38 AM, mshkolnik a crit :
If an import is done and there is anything wrong with the Type field,
it still imports the row but sets Type = Defect. This not good. I
then have to manually correct them all. I would prefer to get an
error. I would like it to default to Unassigned but be a required
field, thus it could not be saved with type set to Unassigned and
would generate errors on import if Type was not properly assigned.
Normally I could set the default under Enumerations and set it as a
required field under Operation Behavior, but Type is in neither
location. Any ideas?
On 1/10/11 7:38 PM, mshkolnik wrote:
This happened to me last week, too. There was an extra space in front
of the type data in our file (" Story"), so we got all defects created.
But it was easy to fix them all in one step. You can change the types
easily either in the web client or the Eclipse client. Here's the
secret for the Eclipse client:
- write a query that returns the work items to be changed
- click on Set to Defaults for the result layout (this puts the Type
field in its own column)
- if you don't see the option to change the Type in the context menu
when you right click in the Type column, go to the Relationships menu
and turn off any options there
The relationships menu is in the down-arrow menu at the top right corner
of the query results view.
If an import is done and there is anything wrong with the Type field,
it still imports the row but sets Type = Defect. This not good. I
then have to manually correct them all. I would prefer to get an
error. I would like it to default to Unassigned but be a required
field, thus it could not be saved with type set to Unassigned and
would generate errors on import if Type was not properly assigned.
Normally I could set the default under Enumerations and set it as a
required field under Operation Behavior, but Type is in neither
location. Any ideas?
This happened to me last week, too. There was an extra space in front
of the type data in our file (" Story"), so we got all defects created.
But it was easy to fix them all in one step. You can change the types
easily either in the web client or the Eclipse client. Here's the
secret for the Eclipse client:
- write a query that returns the work items to be changed
- click on Set to Defaults for the result layout (this puts the Type
field in its own column)
- if you don't see the option to change the Type in the context menu
when you right click in the Type column, go to the Relationships menu
and turn off any options there
The relationships menu is in the down-arrow menu at the top right corner
of the query results view.
If it defaults to Defect then the syntax of your "Type" column did not match what's in RTC. The best way to avoid this is to use an Excel dropdown selector rather than manually typing "Story", for example, only to find the one line that was mistyped as "Stoy" is now a defect. As Mark discovered, even an extra space throws it off. Disappointing this wasn't caught sooner by IBM, but my guess is they don't consider it to be that important compared to other things. I can't really blame them since I dropped it rather than adding it as a defect myself, even though I have added several other defects.
Hi Mike,
Thanks for your answer.
I don't specified the Type in any column, Can you tell me more about that and explain me where I have to put this column?
Is this a column in the csv (where I have the values) or in the xml (mapping xml between my custom fields and the excel or csv)
Thanks in advance.
Regards,
Elisa.
Thanks for your answer.
I don't specified the Type in any column, Can you tell me more about that and explain me where I have to put this column?
Is this a column in the csv (where I have the values) or in the xml (mapping xml between my custom fields and the excel or csv)
Thanks in advance.
Regards,
Elisa.