How queries and views work together
Queries are different from find and search operations.
Although these operations find and retrieve artifacts from the index,
queries can be customized to populate views with artifacts.
Using sample queries
Sample queries gather a broad range of artifacts, from
all artifacts to only one kind, such as change management or requirements
management. You can also run artifact elements queries.
Creating and running queries
Sometimes you need to gather a specific set of artifacts.
You might want to compile a set of failing tests to include in a status
report. Queries can gather a set of artifacts and display the results
for you to act on.
Predefined query parameters
Use the following tables of $parameter_name$ variations
to ascertain date, system parameter, and enumeration properties for
use in parameterized queries.
Using views
Use views to visualize work items, requirements,
design models, and test cases during your product release. Further,
certain views, such as V Process, show the latest status across the
product lifecycle.
Creating a view
Views give teams insight into the state of the key artifacts.
The key artifacts can be test cases, requirements, work items, and
design models. For example, the V Process view shows the lifecycle
of the artifacts, from system design to item integration and test.
Adding and setting up a view in a Jazz project dashboard
You can add and configure one or more widgets in your Jazz™ project dashboard to show one
or more views. You can add any view that displays in My
Views or Shared Views.