No predefined query for "ALL" work items?
I'm wondering why there's no predefined query to simply show *all* work items regardless of state? The only rationale I can think of is that it might not be helpful past a certain number of work items but that doesn't seem like a compelling reason and it's just a guess anyway.
It's no big deal to make such a query but the result has a nonstandard name, cannot be referenced in tutorials, etc. So can anyone on the inside explain the rules for inclusion in "predefined queries"?
MK
It's no big deal to make such a query but the result has a nonstandard name, cannot be referenced in tutorials, etc. So can anyone on the inside explain the rules for inclusion in "predefined queries"?
MK
4 answers
I'm wondering why there's no predefined query to simply show *all*
work items regardless of state? The only rationale I can think of is
that it might not be helpful past a certain number of work items but
that doesn't seem like a compelling reason and it's just a guess
anyway.
It's no big deal to make such a query but the result has a nonstandard
name, cannot be referenced in tutorials, etc. So can anyone on the
inside explain the rules for inclusion in "predefined
queries"?
'All Work Items' might be helpful in tutorials or test setups. But on a
production server, I don't see its usefulness. On jazz.net for instance,
there are 70'000+ work items...
You can still create such a query and add it to the predefined ones using
the corresponding Process Configuration editor 'Predefined Queries'. This
also works for process templates if you want to set up multiple projects
with the same set of custom queries.
--
Regards,
Patrick
Jazz Work Item Team
I'm wondering why there's no predefined query to simply show *all*
work items regardless of state? The only rationale I can think of is
that it might not be helpful past a certain number of work items but
that doesn't seem like a compelling reason and it's just a guess
anyway.
It's no big deal to make such a query but the result has a nonstandard
name, cannot be referenced in tutorials, etc. So can anyone on the
inside explain the rules for inclusion in "predefined
queries"?
'All Work Items' might be helpful in tutorials or test setups. But on a
production server, I don't see its usefulness. On jazz.net for instance,
there are 70'000+ work items...
You can still create such a query and add it to the predefined ones using
the corresponding Process Configuration editor 'Predefined Queries'. This
also works for process templates if you want to set up multiple projects
with the same set of custom queries.
However, in the beginning of a project it can be useful to have a look at all of the WIs, so maybe it would be good to have the predifined query showing all WI? To be honest at the beginning I was looking for a query like this.
kind regards,
Jakub
Agreed. That was my point too. In the long term an "All" query would become less useful but at the beginning it would make life easier. In my case, I started with RTC by running through a number of tutorials, which created predefined work items. Afterwards, I wanted to clean up but queries like "open assigned to me" are of no use when you've got work items assigned to "Markus" and "Kim Cloudburst" (both fictional characters used in tutorials). At this point there are no more than a few dozen work items total, and you want to look through the list and deal with those which do not reflect real work.
MK
MK
However, in the beginning of a project it can be useful to have a look
at all of the WIs, so maybe it would be good to have the predifined
query showing all WI? To be honest at the beginning I was looking for
a query like this.
If you quickly want to see all work item, you can create an empty unsaved
query and just press run, without adding any conditions.
This shouldn't take more than two clicks both in the Eclipse UI and the
Web UI.
--
Regards,
Patrick
Jazz Work Item Team