We have recently added 2 customized attributes, with dropdown list values populated from HTTP filtered Value set, to our customized WI type Defect.
They keep disappearing from the Defect form, seemingly in a random fashion, and to 1 single user in particular. We finally found the pattern:
-
If we open a defect newer than the addition of the field, including creating new defect, as the first WI opening after logging to the RTC, the two attributes always show up, even unassigned.
-
But if we open a defect in existence prior to the addition, as the first WI opening after login, only the attribubutes with assigned values for these two attributes would appear on the defect form,i.e. 1 of the two attribute shows up if only one assigned, and nothing if neither assigned a value.
-
Once into the issue, we will not see those two attributes anywhere.
-
Once that has happened, we have to log out (or close all instances of the browser) of the Jazz tools, and log in and try not commit the same mistake:
-
By opening a newer one
-
Or create a new defect (then cancel). maybe this is the best workaround
Is this intentional for a reason ?
Is there a better way to avoid this than the above steparound ?
Comments
Thanks Sam: Could you put that comment into an answer for me to pick as the right answer. I have tested that fix in DEV successfully, though had to go through some snags as the sync would not work on those with unset mandatory fields.
yes, unset mandatory fields are a pain..
only way is to turn off the advisors during the sync operation.
we see the same with children, dependencies, etc.. where we have enforcement
rule: if u are fiddling with the workitem structure, fields, etc.. turn off all the advisors while you fix it.
it is best to edit the XML and comment them out, least u ill save the exact config.