Share this page
Queries
You can use a query to limit the items that display. Each query is performed on all items in the StarTeam folder and component you have selected. The fields included in the query do not have to display. Once a query has been created, it can be used in every project in the same server configuration.
You can use the following components: Change Request, Requirement, Task, Topic, or Audit Log views.
StarTeam queries have the following attributes:
- A unique name that easily identifies the query. Query names are not case-sensitive.
- Public or private status. Anyone with appropriate access rights can use public queries, while private queries are available only to your user ID. Once a query has been saved with a specific status, its status cannot be changed. However, you can copy a query and change the state of the new query.
- A logical expression appropriate for items of a particular type. These expressions include one or more conditions. A condition consists of a field (not necessarily a current column header), a relational operator, and a value to be compared to the value of the field. For example, a condition used to locate change requests might be:
Responsibility Equals Rhonda Thurman. More complex queries include two or more conditions bound together by logical operators:
AND,OR, andNOT. For example, to locate all the change requests for whichRhonda Thurmanis responsible that also have ahighseverity, use:Responsibility Equals Rhonda Thurman AND Severity Equals High.
Note: If you are creating a complex query, and the first logical operator in your query should be
OR, select the
AND logical operator in the query tree. Then click the
AND->OR->NOT button. This changes an
AND to an
OR. Similarly, one more click changes the
OR to a
NOT. Keep toggling the button until the operator that appears is the one you want to use. It is best to use the condition or logical operation that will result in the fewest matches as the first condition or logical operation.
In this section:
