There are many uses for issue aggregate views, including:
Monorail has flexible list views so that users can accomplish a wide range of common tasks without needing external reporting tools. But, for more challenging understanding tasks, we also offer limited integration with some reporting tools to Googlers.
You can also jump directly to any issue by searching for the issue’s ID number.
owner:me to see issues assigned to you. You might also try
reporter:me. If you are working on a specific component, try
component: followed by the component’s path.
If you are a project member, the project owner may have already configured a default query that will show your issues or a list of high-priority issues that all team members should focus on.
Issue search results pages can be bookmarked, so it is common for teams to define a query that team members should use to triage incoming issues, and then share that as a link or make a short-link for it.
You can refine a query by editing the query terms in the search box at the top of the page. You can add more search terms to the end of the query or adjust existing terms. The autocomplete menu will appear if you position the text cursor in the existing query term. One common way to adjust search terms is to add more values to an existing term by using commas, e.g.,
A quick way to narrow down a displayed list of issues is to filter on one of the shown columns. Click on the column heading, open the
Show only submenu, and select a value that you would like to see. A search term that matches only that value will be added to the query and the list will be updated.
Sort up or
Labels defined by the project owners will sort according to the order in which they are listed on the label admin page, e.g., Priority-High, Priority-Medium, Priority-Low. Teams are also free to use labels that make sense to them without waiting for the project owner to define them, and those labels will sort alphabetically.
To sort on multiple columns, A, B, and C: First sort on column, C, then B, and then A. Whenever two issues have the same value for A, the tie will be broken using column B, and C if needed.
For multi-valued fields, issues sort based on the best value for that field. E.g., if an issue has CC’s for
email@example.com, it will sort with the A’s when sorting up and with the H’s when sorting down.
Project owners can specify a default sort order for issues. This default order is used when the user does not specify a sort order and when there are ties.
... menu located after the last column heading in the issue list.
Alternatively, you can hide an existing column by clicking on the column heading and choosing
You can copy and paste from an HTML table to a Google Spreadsheet:
For longer sets of results, project members can export CSV files:
CSV link at the bottom of the issue list. A file will download.
The exported CSV will only contain data on that page. If the list is longer than one page either shorten the search result or go to the next page and click the
CSV link again. You can also increase the pagination size to 1000 to include more results per page by adding &num=1000 to the query parameter
The issue list can group rows and show a group heading. For example, issues could be grouped by priority. To group rows:
Each section header shows the count of issues in that section, and sections expanded or collapsed as you work through the list.
Bulk edit from the controls above the issue list.
Monorail’s issue grid is similar to a scatter chart in that it can give a high-level view of the distribution of issues across rows and columns that you select.
Grid in the upper-left above the issue list table.
You can also set the level of detail to show in grid cells: issue tiles, issue IDs, or counts. Tiles give the most details about issues, but only a limited number of tiles can fit most screens. If issue IDs are shown, hovering the mouse over an ID shows the issue summary. Counts can be the best option for a large set of issues, and clicking on a count link navigates you to a list of specific issues.
Note: Because some issue fields can be multi-valued, it is possible for a given issue to appear in multiple places on the issue grid at the same time. The total count shown above the grid is the number of issues in the search results, even if some of them are displayed multiple times.
Monorail’s chart view is a simple way to see the number of issues that satisfy a query over a period of time, which gives you insights into issue trends. Monorail uses historical data to chart any query made up of query terms that we support in charts. Unlike many other reporting tools, you do not need to define a query ahead of time. To see a chart:
Chart in the upper-left above the issue table.
One of the most important issue trends is the trend toward zero as a team works to resolve a set of issues related to some upcoming milestone or launch. Monorail can add a prediction line to the chart, which is commonly called a burndown chart. Here’s how:
Chart in the upper-left above the issue table.