Found In attribute with tasks?
We use a process template based on Scrum 2.0, and the Tasks work items don't have a Found In attribute, at least in the editor presentations.
But if I write a query to search for Tasks with a Found In certain value, I get 25 out of all 5,000 tasks returned as if that attribute exists and has that value. How does that attribute get filled in with the value in the query? What am I missing here? Thanks! Mark |
3 answers
Ralph Schoon (63.1k●3●36●46)
| answered Mar 15 '10, 3:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Mark,
I always had a found in attribute at least for the execution items. I believe this is also true for SCRUM 2. that some of the work items have the attribute set supports that. It is usually on the details tab which is shared. Could someone have changed the editor presentation in the Projects Process Configuration> Project Configuration>Configuration Data>Work Items>Editor Presentations or Editor Presentation Bindings? You could fix it there too. Do the other ones have the attribute as unassigned? If that is the case the attribute is still there but might not be visible in the presentation. Ralph We use a process template based on Scrum 2.0, and the Tasks work items don't have a Found In attribute, at least in the editor presentations. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Mar 15 '10, 11:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In my experience, the most common way for a work item to get
"unexpected" attributes is for the work item to be first created as a type of work item that does have that attribute, and then to have its type changed to a new type that does not have that attribute (in which case the attribute is no longer visible, but still exists on the work item). Cheers, Geoff rschoon wrote: Hi Mark, |
|
On 3/15/10 10:12 AM, Geoffrey Clemm wrote:
In my experience, the most common way for a work item to get Boy, I really thought that was going to be it. But when I checked the history of one of these work items, it shows that the work item was created as type Task at the same time the Found In field is set. Since that field isn't in the editor presentation, I'm still confused on how these are getting set. Our users don't have the permissions to change the process configuration, so I don't think editor changes could have happened. It looks like the remaining task work items have the Found In attribute set to Unassigned. Now there are 29 work items with it set, 2899 tasks with it unassigned. The only other possibilities I've thought of are CSV imports, or REST API calls. Mark |
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.