Master Jira Search & Jira Query Language (JQL)

A high level overview of how searching in Jira works. At the end you'll have a solid understanding of fundamental concepts you'll need to find this successfully.

This lecture covers some basic information about the Basic Search feature in Jira, including:

• Who should use it

• How to find it

• How to customize it

This lecture covers how to create and save a search in Jira, including the importance of having a good description and how to ensure appropriate permissions are applied to your search.

This course covers how to share searches, including via URL and the Saved Filter function. At the end, you'll be able to share any search you create with anyone on your team, and troubleshoot some common challenges.

Sometimes it's just quicker to share the URL!

This lecture outlines how to subscribe to a saved search in Jira, as well as some common use cases where this feature is useful, including:

• Morning reports of how the system is doing

• Bi-weekly sprint updates

• Urgent/high priority tickets

• and more

This lecture covers some common challenges you'll run into when working with Jira searches. These include folks not being able to view your saved search, tickets "missing" from the search and more.

This lecture goes over what advanced search and JQL are. You'll get a good understanding of the background of this feature, when it can/should be used and more.

This lecture covers the order of a JQL query : Field - Operator - Value. Understanding this pattern will allow you to quickly and easily write valid JQL queries, and avoid common errors.

This lecture covers fields and operators that are available in JQL. By the end, you'll understand the basic operators, and how to use them.

This lecture covers how to work with timestamps in Jira, including the format (dd-mm-yyyy) and some functions to help make searches more dynamic, including:

• startOfDay()

• startOfWeek()

• startOfMonth()

• and more

This lecture covers the keywords used in JQL. These allow you to combine multiple criteria, for example, finding all issues with a specific issuetype AND having the same reporter. Includes the following:

• AND

• OR

• NOT

• EMPTY

• IN

• ORDER BY

Learn about the importance of parenthesis in this lecture. By the end, you'll understand why they're important, and how to use them to improve your search results.

Searching for text within Jira can be tricky, but by the end of this lecture you'll understand how it works, and some common issues with it.

The Order By clause allows you to control the order of your results - but it must be added at the end of the query.

In addition to searching for specific fields, JQL also includes a number of functions to make your searches more powerful. Examples include "startOfDay()", "linkedIssues" and "openSprints()". By the end of this lecture you'll understand what they are, how they work and when to use them.

This lecture reviews some useful searches specifically for Jira Service Management (e.g. a help desk). Here you'll learn how to search for tickets about to breach their SLA as well as aging tickets.

This lecture reviews some useful searches specifically for springs and versions.

Rovo is Atlassian's AI tool and offers several ways to find things in Jira more easily.

Get hands-on and see how to use Rovo to find things in Jira.

You can interact with Rovo via chat - this opens up some interesting ways to find things in Jira beyond the general search.

Rovo agents focus on specific tasks - like finding specific work items. Learn about them here!

This lecture provides an overview of what a Dashboard is, and why you'll find them useful. You'll understand some common use cases and learn where to create them.

During this lecture we'll build a basic dashboard. You'll end the lecture understanding the entire process, from building the filters to create and sharing the final product.

This lecture provides a high-level overview of various SLA functions available. This group of functions allows you to quickly find tickets based on their SLA (which are setup by the project admin), and make managing and tracking SLA's significantly easier.

This function finds tickets that have a specific SLA in the Breached state - it is exceeding its current SLA. Note that if the SLA is reset (based on rules the Project Admin sets up) this function will not find the ticket (see EverBreached instead).

This function finds tickets that has ever had a specific SLA in the Breached state. This includes tickets that Breached their SLA, then had that SLA reset. For tickets currently in the Breached state, see Breached.

This function finds tickets that have a specific SLA in the Completed state. This is defined by the Project Admin, but is generally something like reaching a specific status (e.g. "Done") or other action ("Comment to customer").

This function finds tickets that have a specific SLA in the Paused state. The Project Admin defines these rules, but SLAs are commonly paused if a ticket is in a specific status (e.g. "Waiting for customer"). This is done to avoid penalizing the Agent if they waiting action from someone else.

This functions finds tickets where a specific SLA has a specified amount of time remaining before it exceeds its target. For example this could find tickets that have under 2 hours until they breach a specific SLA.

These functions find tickets that have a specific SLA clock ticking.

• Running - Returns tickets regardless of the calendar they use

• WithinCalendarHours - Returns tickets only if the underlying calendar is active

Example

A calendar is active from 9-5, Monday to Friday.  You are searching for tickets at 6 PM on Tuesday.

• Running - will return any ticket with an SLA clock ticket

• WithinCalendarHours - Will NOT return tickets as you're outside the calendar's hours

This functions finds tickets where a specific SLA has run for a specified amount of time. For example this could find tickets have an SLA running for over 10 hours.

A high level overview of what approval functions are for and which ones there are in Jira.

The Approved function returns any ticket that has an approval in the approved status

The Approver function lets you find tickets that have one or more specific approvers listed on them

The myApproval function returns any ticket where the current user needs to provide, or has ever provided, approval. Very useful for sharing with approvers to keep track of their tickets.

The myPending function returns any ticket where the current user needs to provide, or has ever needed to provide, approval. Very useful for sharing with approvers to keep track of their tickets.

The pending function returns any ticket that is pending approval.

The pendingBy function returns any ticket pending approval be a specific user or users. Useful for keeping tabs on specific approvers.

The myPendingApproval function returns any ticket where the current user needs to provide approval. Very useful for sharing with approvers to keep track of their tickets.

An overview of what sprints and releases are. These concepts are important to understand as they inform your search.

The closedSprint function returns tickets in a closed (completed) Sprint. Helpful for tracking tickets that were planned to have been completed (but maybe haven't been!) and for reporting out on work.

The earliestUnreleasedVersion function returns tickets in the most immediate upcoming Release (NOTE - this is defined as the one at the bottom of the Release list and doesn't consider the date listed in Jira!). Useful for seeing what is upcoming.

The futureSprints function returns tickets in future (planned) Sprints. Helpful for seeing what is coming up and seeing what work may be spilling from one Sprint to another.

The releasedVersions() function returns tickets that are part of a released (completed) version. Helpful in tracking tickets that have already been released.

The openSprints function returns tickets in a open (ongoing) Sprint. Helpful for tracking tickets that are actively being worked on, as well as ones that have spilled into new Sprints.

The unReleasedVersions() function returns tickets that are part of an unreleased (upcoming) version. Helpful in tracking tickets that are planned for future work.

This lecture wraps up our course! We'll review what we've done, and cover what's next in your Jira journey.

Jira uses "query string completion" to pass searches to its server. This means you can dynamically create searches based on outputs of a google or excel function. Learn how to use this great trick in this lecture!

This google sheets add-on allows you to import Jira data directly to your google sheets - no more downloading and uploading! Plus, you can schedule it to run on a cadence, making your reporting life even easier.