How to Use the Jira JQL Filter Builder Prompt to Turn Morning Standup Questions into Saved Filters

Most team leads open Jira every morning with the same handful of questions. What is assigned to me? What is stuck in review? What is blocked? What rolled over from last sprint? Answering those by clicking through boards takes time, and the answers change depending on who looks. The Jira JQL Saved Filter and Dashboard Builder: Team Queries for My Open Work, Blocked and Aging Issues, Sprint Carryover, Filter Subscriptions, and Gadget Layout prompt turns those plain questions into saved JQL filters, a dashboard layout, and email subscriptions built on your real field and status names.

What the prompt produces

1. A saved filter for each question, with a name, the JQL, and a line on what it returns.
2. Field name checks that show when to quote a custom field or use its ID.
3. Aging and blocked queries using statusCategory, status changed, updated, and Flagged with clear date windows.
4. A sprint carryover filter using openSprints() and closedSprints().
5. A dashboard gadget layout that maps each filter to a gadget and column order.
6. Filter subscriptions with schedules, recipients, and whether to send when empty.
7. Sharing settings for each filter and dashboard.
8. A pitfalls list that tells you what each filter will miss.

How to fill the inputs

ProjectsAndStatuses needs the project keys, issue types, and every workflow status with its status category. The category matters. Filtering on statusCategory != Done is shorter and more reliable than listing six status names, and it keeps working when someone adds a new status.

CustomFields should say which fields the team relies on and whether each one is company managed or team managed. Team managed fields can behave differently in cross project searches, and the prompt flags that.

TeamQuestions is just a plain list, written the way people actually ask. "What has been in review more than 2 days" is a perfect input.

BoardSetup tells the prompt whether you run Scrum or Kanban, how long sprints are, and what the board filter is. The carryover filter only makes sense with sprints.

Audience separates what a manager wants emailed from what developers want on a dashboard.

Reading the example output

The example covers a payments team with two projects and a shared Team field.

• "My open work" uses assignee = currentUser() and statusCategory != Done, so one shared filter works for every developer.
• "In Review over 2 days" uses status changed to "In Review" before -2d, which measures time in the status rather than time since the last edit.
• The blocked filter combines Flagged with a Waiting on Vendor status.
• The carryover filter returns issues that sit in an open sprint and also appeared in a closed one.
• The pitfalls section warns that issues with an empty Team field silently drop out of every query, and suggests a weekly check for them.

Tips for better results

• Paste status names exactly as Jira shows them, including capitals and apostrophes. Small mismatches cause empty results.
• Test each filter in the issue search screen before adding it to a dashboard.
• Send subscriptions even when the result is empty. An empty email tells the manager there is nothing blocked, while no email leaves them guessing.
• Put the team name at the start of every filter name so filters stay easy to find in a large site.

Mistakes to avoid

• Do not rely on updated alone for aging. A single comment resets it, so pair it with status changed when you can.
• Do not share filters with everyone on the site if they include sensitive projects; share with a project role instead.
• Do not forget that resolved statuses like Won't Do usually sit in the Done category and disappear from open work views.

Who it is for

Scrum masters, engineering managers, Jira administrators, and team leads who want consistent answers to daily questions without building a dashboard by trial and error.

A practical setup order

Start with the "my open work" filter and the blocked filter, since those get used every day. Add them to a shared dashboard and ask the team to use it for a week. Then add the aging and carryover filters and set up the Monday subscription. Review the pitfalls list once a month, because fields and statuses change as the team's workflow grows.

Related PromptDig links

Open the Jira JQL Saved Filter and Dashboard Builder: Team Queries for My Open Work, Blocked and Aging Issues, Sprint Carryover, Filter Subscriptions, and Gadget Layout prompt with your project setup and questions. For more productivity prompts, Browse more prompts. If you have a dashboard recipe your team loves, Share a prompt.