JQL — Jira Query Language

JQL-Tips

JQL, which stands for Jira Query Language, is one of the most powerful features built within Jira. It specifically enables you to go beyond basic search; instead of (endlessly) scrolling through issues, you can filter, search and complete organize items in your project data with precision. You can search for all issues assigned to a teammate, you can find items that have been stuck in a certain status, or you can pull up work logged in the last 28 days and have JQL do the work for you. Once you know a few everyday queries, you will save time, you will be able to identify bottlenecks quickly, and you will be able to keep project on track.

Below are some practical JQL examples that you can start using right away to streamline your workflow.

1. Find all issues assigned to a specific user

assignee = jdoe

Finds all issues assigned to jdoe.

2. Find all open issues in a specific project

project = "My Project" AND status in ("To Do", "In Progress")

Shows all issues in My Project that are either To Do or In Progress.

3. Find issues that are due today

due = startOfDay()

Finds all issues that are due today.

4. Find all issues created in the last 7 days

created >= -7d

Finds issues that were created within the last 7 days.

5. Find all issues with a specific priority (e.g., High)

priority = High

Filters all issues that are marked with High priority.

6. Find all issues of a specific type (e.g., Bug)

issuetype = Bug

Shows all Bug type issues.

7. Find unresolved issues assigned to a user

assignee = jdoe AND resolution = Unresolved

Shows all unresolved issues assigned to jdoe.

8. Find issues with a specific label

labels = "UI-issue"

Filters issues with the label UI-issue.

9. Find issues that have not been updated in the last 2 weeks

updated <= -2w

Finds issues that haven’t been updated in the last 2 weeks.

10. Find issues linked to a specific issue

issue in linkedIssues("PROJ-123", "blocks")

Shows issues that are blocked by PROJ-123.

11. Find all issues due in the next 7 days

due <= 7d

Filters issues that are due within the next 7 days.

12. Find all issues that are assigned to no one

assignee IS EMPTY

Shows all unassigned issues.

13. Find issues updated by a specific user

updatedBy = jdoe

Filters issues that were last updated by jdoe.

14. Find issues with a specific Epic Link

"Epic Link" = "EPIC-123"

Filters issues that are part of the Epic EPIC-123.

15. Find unresolved issues assigned to a specific person

assignee = jdoe AND resolution = Unresolved

Shows unresolved issues assigned to jdoe.

16. Find issues with a specific status transition (e.g., from “To Do” to “In Progress”)

status CHANGED FROM "To Do" TO "In Progress"

Finds issues that transitioned from “To Do” to “In Progress”.

17. Find issues created in a specific time period (e.g., last month)

created >= startOfMonth(-1) AND created <= endOfMonth(-1)

Filters issues created in last month.

18. Find issues where the summary contains specific text

summary ~ "login"

Finds issues with “login” mentioned in the summary.

19. Find issues in a project that are either “To Do” or “In Progress”

project = "My Project" AND status IN ("To Do", "In Progress")

Filters issues in My Project that are either “To Do” or “In Progress”.

20. Using Wildcards

summary ~ "bug*"

*Asterisk ()**: This is a wildcard character used for matching patterns. Finds issues with summaries that start with “bug”.

21. Parent-Child Relationship

parent = "PROJ-123"

Finds subtasks of the issue PROJ-123.

22. Issues with specific link types

issue in linkedIssues("PROJ-456", "blocks")

Finds issues that block PROJ-456.

23. Worklog queries

worklogAuthor = jdoe

Finds issues where jdoe logged time.

24. Time spent

timespent > 3600

Finds issues where more than one hour (3600 seconds) has been logged.

25. Custom Field Queries

cf[10001] = "Custom Field Value"

Finds issues where the custom field with ID 10001 has the value “Custom Field Value”.

Conclusion

JQL turns Jira from a simple tracking tool into a powerful query engine. With the examples above, you can filter issues by assignee, date, status transitions, custom fields, and more — giving you exactly the visibility you need.

The key is to start small: take one or two queries that solve your daily pain points, and gradually build complexity from there. Before long, you’ll be writing JQL like second nature and driving better insights, faster decisions, and smoother workflows.

If you want to make the most of JQL and Jira reporting, explore how RVS Softek can help you simplify queries, automate reports, and unlock even deeper project insights. Book a Demo Now !

Originally published at https://www.rvssoftek.com.