Quick Start

https://youtu.be/0tfasoF8V8Q

Step 1: Create a spreadsheet of the users and managers you want to include

If you don’t have any headings, the first column will be treated as the users and the second column their managers.

If you do use headings, the user heading must be user and the manager heading must be manager. Here’s an example Google Spreadsheet:

Step 2: Click on Update Org Data and add org data

Click on the “Update Org Data” card

Then click on the “Add Org Data” button:

Copy your spreadsheet data and paste into the editor and click “Save”

Step 3: Test your data

Click on the “Test Org Data” tab and enter a query using your org data. OrgJQL defines an orgOf JQL function that takes a manager’s name and returns a list of everyone who rolls up to them. Here’s an example query:

assignee in orgOf("William MacLane")

Verify the expansion is correct.

• Understanding Forthic

• Tweaking a Leaderboard

• Tweaking an Issue Graph

Review JQL Executions

In 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.

https://youtu.be/DivmtPQViM0

Background on JQL Executions

When 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 clauses

You can filter the table by clauses:

Refreshing expansions

You can click on the “Refresh” control for each clause to force update an expansion:

When are Precomputations Updated?

The following trigger OrgJQL precomputation updates:

• Ticket is created (after 15 minutes of inactivity)

• Ticket is updated (after 15 minutes of inactivity)

• OrgJQL data is updated

• Custom JQL function code is updated

• When “Refresh All” is clicked in the “Review JQL Executions” page

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 Job

You can stop a running precomputation job by clicking “Force Stop”: