...
| Expand | ||||
|---|---|---|---|---|
| ||||
Using Rovo to create manager-specific reportsIn OrgJQL, all one-off reports are built for a given “root manager”. This is the top level manager for the report. Every report has an “Org Chart Control” that allows you to drill up and down into the org:  When you select a manager, all issues in the report are filtered to that manager. Creating a basic reportTo get to the OrgJQL Assistant, click on “Chat” at the upper right of the window, then on “Browse Agents”, and then select “OrgJQL Assistant”. To create a basic report for a manager (essentially, just the org information) you can enter the following into the Rovo chat:
The OrgJQL Assistant will return a link that shows you the org control for that manager Adding issues to your reportTo add issues to an existing report, type something like:
The OrgJQL Assistant will create a new link to a report using that JQL to pull issues. If there are issues in your report, you’ll see an “Issues Table” bottom in sidebar at the left:  Clicking this will display an issues table filtered by the selected manager. The selected manager is shown in purple at the top of the Issue Table:  The shortcut for toggling the issue table is: |
| Expand | ||
|---|---|---|
| ||
Using Rovo to Create LeaderboardsA Leaderboard is a component that rolls issues up by manager and slices them by another dimension. By default, the values in a leaderboard are issue counts, but that can be changed to another statistic (e.g., Story Points, Average Days Late, Max Days Late, etc.) To add a leaderboard to an existing report, type something like this into the OrgJQL Assistant chat:
Rovo will response with a new link that has the leaderboard in it.  Clicking on a pie slice or cell will select all issues in that go into that. These will be highlighted in orange.  If some but not all issues in an element are selected, the label will be shown in italics:
All selected issues are indicated in the sidebar
Clicking on this control brings up the Issue Table:  |
Administration
| Expand | ||
|---|---|---|
| ||
Review JQL ExecutionsIn this section, we'll go over how to view and manage OrgJQL executions. These "expansions" are stored by Jira for performance, but they are updated when issues are created or updated or when org data is changed. You can also force update any or all OrgJQL executions here. Background on JQL ExecutionsWhen a JQL function is executed, it expands into a JQL fragment that is substituted into the query.  Jira stores these expansions in a pre-computations database to improve performance. The expansions for OrgJQL are listed in the table of the “Review JQL Executions” page. Searching for clausesYou can filter the table by clauses:  Refreshing expansionsYou can click on the “Refresh” control for each clause to force update an expansion:  When are Precomputations Updated?The following trigger OrgJQL precomputation updates:
The refresh job is asynchronous and runs from a queue, so only one job is ever running at a time. NOTE: Precomputations are only updated if their values have changed. Stopping a Precomputation Refresh JobYou can stop a running precomputation job by clicking “Force Stop”:  |
...