Available Reports

Custom Query

Compose a new ticket query by selecting filters and columns to display.

SQL reports and saved custom queries Sort by: Identifier Title

{1} Active Tickets

  • List all active tickets by priority.
  • Color each row based on priority.

{2} Active Tickets (short)

  • List all active tickets by priority.
  • Do not show component, version and status. The rest is the same as report {1}

{3} All Tickets by Milestone

This report shows how to color results by priority, while grouping results by milestone.

Last modification time, description and reporter are included as hidden fields for useful RSS export.

{4} Assigned, Active Tickets by Owner

List assigned tickets, group by ticket owner, sorted by priority.

{5} Assigned, Active Tickets by Owner (Full Description)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

{6} All Tickets By Milestone (Including closed)

A more complex example to show how to make advanced reports.

{7} My Tickets

This report demonstrates the use of the automatically set $USER dynamic variable, replaced with the username of the logged in user when executed.

{8} Active Tickets, Mine first

  • List all active tickets by priority.
  • Show all tickets owned by the logged in user in a group first.

{9} Project management

See here tickets with component set to Project management

{12} My Tickets by Milestone

As Tickets by Milestone only for the user which is logged in.

{14} Milestone 4.2

Tickets in milestone 4.2

{15} Milestone 4.3

Show tickets in milestone ORCHIDEE 4.3

{16} Milestone 4.4

Show tickets in milestone 4.4 (including closed tickets)

{17} Milestone 4.5

Show tickets in milestone ORCHIDEE 4.5 (including closed tickets).

{18} Different pixel areas and texture for simulation over one pixel vs. the same pixel but within a 2 simulation

Driver:

dim2_driver offline driver

Problem title:

Incorrect pixel area in single-pixel simulations

Problem description:

The reported area of a pixel is not correct when using a 1x1 grid. For mid-latitude pixels at 2-dergree resolution, the area is off by about a factor of 3 compared to what is reported for the same pixel when using a larger grid. This is an issue as of today (trunk@8075) and likely has always been the case, but the earliest revision I've checked is trunk@7004. Tested with IOIPSL/tags/v2_2_5@6273, trunk/libIGCM@1581, XIOS2/trunk@2439

Note: See TracReports for help on using and creating reports.