It's all about the answers!

Ask a question

Filed Against should default to Unknown for new work items


Scott Chapman (3216547) | asked Nov 03 '11, 3:20 p.m.
I sometimes see it default to the first in the list, rather than Unknown.

Is there a way to specify this?

6 answers



permanent link
Lawrence Smith (3764) | answered Nov 03 '11, 11:15 p.m.
JAZZ DEVELOPER
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?

permanent link
Scott Chapman (3216547) | answered Nov 04 '11, 10:57 a.m.
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...

permanent link
Lawrence Smith (3764) | answered Nov 04 '11, 12:54 p.m.
JAZZ DEVELOPER
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...

permanent link
Scott Chapman (3216547) | answered Nov 04 '11, 1:11 p.m.
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...

permanent link
Lawrence Smith (3764) | answered Nov 04 '11, 1:46 p.m.
JAZZ DEVELOPER
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...

permanent link
Scott Chapman (3216547) | answered Nov 04 '11, 1:50 p.m.
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...

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.