Search, exports and reports
Search Jira with JQL or plain English, choose columns and save searches, export to Excel, CSV, JSON, Markdown or Word, and generate PDF or HTML reports.
Last updated
On this page
Two parts of the app work with Jira search results: Search & Automate, to find, shape and act on issues, and Advanced Export, to turn a JQL query into a file or a report. From a board or a backlog, the ••• menu's Laya WorkflowOS item opens Advanced Search.
Search & Automate
- Type JQL with live checking and autocomplete, or, with AI help on, describe the search in plain English. Then choose Run.
- Search runs as you, so results only include issues you can browse in Jira.
- Choose Columns to add or remove any field, custom fields included. Drag columns to reorder them, sort by them, and switch the row density.
- Save keeps the search with its columns, sort and density, as a chip above the results. Saved searches are yours alone.
- Export the current view to CSV in your browser, or export every matching issue, with these exact columns, in the background.
- Dry-run a rule over these results shows what a published rule would do to the issues found.
- Create rule from this search turns the search into a scheduled rule.
Everyone can search and export the current view. Exporting every matching issue, dry runs and new rules need permission to manage rules.
Advanced Export
- Open Advanced ExportGive it a Name (optional) and set Type to export or report.
- Pick the formatFor an export: Excel (.xlsx), CSV, JSON, Markdown (.md) or Word (.docx). For a report, see reports.
- Enter the JQLType the JQL, or describe it in plain English. Preview shows the matching issues; Load more shows the next page.
- GenerateChoose Generate export or Generate report. The file is made on Atlassian in the background and appears in Recent files, where you can download, preview or delete it.
Reports
Set Type to report, choose a Report and a Format (PDF or HTML), and enter the JQL that decides which issues it covers. Reports include charts, KPI tiles and tables.
| Report | What it shows |
|---|---|
| Master report (all-in-one) | Many report sections in one document, like a binder. |
| Board status breakdown | Issue counts by status and assignee. |
| Status category (To Do / In Progress / Done) | How work splits across the three status categories. |
| Sprint summary | Sprint scope, open and done work, by assignee and status. |
| Workload by assignee | Open issues per person, and high-priority load. |
| Throughput (recent delivery) | Issues resolved recently. |
| Created vs Resolved | Inflow and outflow over time. |
| Overdue & due soon | Issues that are overdue or due soon. |
| Aging issues, Unresolved aging bands, SLA / aging | How long open work has waited. |
| Stale issues (no recent activity) | Issues with no recent update. |
| Unestimated issues | Issues missing estimates. |
| Breakdown by priority, component, label, fix version, epic or resolution | Issue volume split by that field. |
With AI exec-summary on (the default for reports), AI adds a plain-English summary at the top. Choose the chip to turn it off. See AI summaries on reports.
| Goal | Report | JQL |
|---|---|---|
| Sprint review | Sprint summary | project = ABC AND sprint in openSprints() |
| Weekly workload | Workload by assignee | project = ABC AND statusCategory != Done |
| Stale work | Stale issues (no recent activity) | project = ABC AND statusCategory != Done AND updated <= -14d |
| Project health pack | Master report (all-in-one) | project = ABC |
Rules can create exports and reports too, with the Export search results and Generate a report actions, for example on a weekly schedule.
Email support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.