TQL-Definition

Examples:

• State != opened
  

• Lastedit < DATE(2003-01-01)
  

• Project NOT_LIKE "Foo%"
  

• ORDER_BY OriginatorFirstname DESC, State ; ItemNo > 0
  

• (Created OLDER_THAN 20 DAYS) AND State == opened
  

• Project == "Southpark" AND OwnerLastname == "Cartman"
  

• (ManagerLastname == "Cartman" OR ManagerLastname LIKE "Mc%") AND(Lastedit OLDER_THAN 2 DAYS) AND Project == "Southpark" AND (Created > DATE(1999-12-24) AND (State == opened OR State == suspended))

Note: all localized attribute values need to be stated as you see them in your GUI. E.g. if you see the German GUI you need to specifiy "State != geöffnet" instead of "State != opened" for the English interface. All values, fields, and attributes are case sensitive.

Fields:

• Build
  

• ChangedByFirstname
  

• ChangedByLastname
  

• Class
  

• Created
  

• Description
  

• EndDate
  

• ItemNo
  

• Lastedit
  

• List
  

• ManagerFirstname
  

• ManagerLastname
  

• OriginatorFirstname
  

• OriginatorLastname
  

• Priority
  

• Project
  

• ReleaseNoticed
  

• ReleaseScheduled
  

• ResponsibleFirstname
  

• ResponsibleLastname
  

• Severity
  

• StartDate
  

• State
  

• Subsystem
  

• Synopsis

Sorting:

• ORDER_BY field1 [ { DESC | ASC } ] [, field2 [ { DESC | ASC } ]...] ; TQL

Functions:

• DATE(yyyy-mm-dd [hh[:mm[:ss]]])

Operators:

• ==
  

• !=
  

• >=
  

• >
  

• <=
  

• <
  

• LIKE
  

• NOT_LIKE
  

• OLDER_THAN integer [ { HOURS | DAYS | WEEKS | MONTHS | YEARS } ]
  

• NEWER_THAN integer [ { HOURS | DAYS | WEEKS | MONTHS | YEARS } ]

Report Repository

You can save your TQL queries in the database by clicking the "New" button in the Repository section of the screen. In addition to the TQL definition itself you need to assign a name to it by which it can be referenced later on.

There are actually three repositories for TQL definition:

• your own, personal TQL definition repository

• a public TQL definition repository

• a project specific TQL definition repository

You may add, modify and delete TQL definitions from your private repository as you like. There is no limit on the number of definitions that you can store.

You can copy a definition from your private repository to the public repository, and remove it from there. This is a convenient way to share your TQL definitions with others. You can select existing TQL definitions from the public repository and execute them. You can copy them to your own private repository. You can filter the publicly visible TQL definitions by their authors.

If you have project administrator rights you can create TQL expressions that are being used often in the project for the entire project staff. Each person having read access to the project will also have access to these TQL definitions and may execute them and copy them to their own repository. You can filter the project specific TQL definitions by project name.