Whether and where the imported values for attributes, unassociated with the WI type on the import, would be stored in the DB ?

long TRUONG (365●4●113●145) | asked Feb 25 '14, 11:09 a.m.

We have accidentally imported (with CSV file) values to attributes unassociated with the WI type specified in the import data.

We were surprised to find these values showed up as imported on queries:

The values are written to the DB somewhere ?
And actually associated to that WI type, even though not configured so ?
Does this apply only to customized attributes, which are stored together in table(s) of schemas different than those of OOTB attributes.
The values would show up on the form if the attributes in question are added to the WI type and its presentation later, after the import ?

Accepted answer

permanent link

Geoffrey Clemm (30.1k●3●30●35) | answered Feb 25 '14, 11:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Yes, yes, no (it applies to all attributes, no just custom ones), and yes.
One reason it is designed this way is that you are allowed to change the "type" of an existing work item, as well as modify the definition of an existing work item type, so any attribute might become valid at some point.

long TRUONG selected this answer as the correct answer

Comments

long TRUONG commented Feb 25 '14, 11:43 a.m.

Thanks Geoffrey: Interesting design. OOTB (="never in the box before" here) vision ? :)

long TRUONG commented Feb 25 '14, 11:55 a.m.

Forgot to mention, (Quickdraw) Geoffrey, that this has been the quickest answer I have seen, within 10 min.

Geoffrey Clemm commented Feb 25 '14, 12:26 p.m.

FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

(:-)

It's all about the answers!

Related questions

Whether and where the imported values for attributes, unassociated with the WI type on the import, would be stored in the DB ?

Accepted answer

Your answer