Filed Against should default to Unknown for new work items

If you mean "Undefined", then "Undefined" should always be the first in the list and the other items should be in the order that they appear in the category tree... however, maybe if the Admin specified "Restrict category visibility" to the teams associated with the Undefined category, and you are not on that team, then maybe you don't see it on the list.

If you mean "Unknown" then this would be a category added by the admin and can be anywhere in the list.

I suspect the change is per project area and you are seeing the result of visibility per team, but I haven't tried it.

Larry Smith

I sometimes see it default to the first in the list, rather than Unknown.

Is there a way to specify this?

If you mean "Undefined", then "Undefined" should always be the first in the list and the other items should be in the order that they appear in the category tree... however, maybe if the Admin specified "Restrict category visibility" to the teams associated with the Undefined category, and you are not on that team, then maybe you don't see it on the list.

If you mean "Unknown" then this would be a category added by the admin and can be anywhere in the list.

I suspect the change is per project area and you are seeing the result of visibility per team, but I haven't tried it.

Larry Smith

Sorry, I wasn't accurate. I am talking about th value "Unassigned". It appears to be built in, and is sometimes used but not always...

And of course I meant "Unassigned" too :-)

If you mean "Undefined", then "Undefined" should always be the first in the list and the other items should be in the order that they appear in the category tree... however, maybe if the Admin specified "Restrict category visibility" to the teams associated with the Undefined category, and you are not on that team, then maybe you don't see it on the list.

If you mean "Unknown" then this would be a category added by the admin and can be anywhere in the list.

I suspect the change is per project area and you are seeing the result of visibility per team, but I haven't tried it.

Larry Smith

Sorry, I wasn't accurate. I am talking about th value "Unassigned". It appears to be built in, and is sometimes used but not always...

And of course I meant "Unassigned" too :-)

So, I have noticed that if I create a work item from a plan, it gets sets to the first value rather than unassigned. Most other places seems to work...

I see you opened
183307: Files against not set to Undefined when new work item created from plan view

for this... thanks!

Larry

And of course I meant "Unassigned" too :-)

So, I have noticed that if I create a work item from a plan, it gets sets to the first value rather than unassigned. Most other places seems to work...

I see you opened
183307: Files against not set to Undefined when new work item created from plan view

for this... thanks!

Larry

So, I have noticed that if I create a work item from a plan, it gets sets to the first value rather than unassigned. Most other places seems to work...

No Charge. Seemed like a bug to me...