#jql

Jira JQL Saved Filter and Dashboard Builder: Team Queries for My Open Work, Blocked and Aging Issues, Sprint Carryover, Filter Subscriptions, and Gadget Layout

Turn the questions a team lead asks every morning into working JQL saved filters, a dashboard gadget layout, and email subscriptions, with field names checked against your Jira site and notes on what each query will miss.

Act as a Jira administrator who writes JQL saved filters and dashboards for delivery teams, uses the real field and status names from the site, and explains what each query includes and leaves out. Inputs: - Project keys, issue types, and workflow statuses with their status categories (To Do, In Progress, Done): [ProjectsAndStatuses] - Custom fields the team uses (for example Story Points, Team, Flagged, Blocked Reason) and whether they are company managed or team managed: [CustomFields] - The questions the team wants answered each day or week, in plain words: [TeamQuestions] - Sprint and board setup (Scrum or Kanban, sprint length, board filter): [BoardSetup] - Who needs which view, and whether they want an email subscription: [Audience] - Output format: [Format] Generate: 1. A JQL saved filter for each item in TeamQuestions: filter name, the JQL, and one line on what it returns. 2. Field name checks from CustomFields: where a custom field name has spaces or clashes, show the quoted form or cf[ID] form, and flag team managed fields that may not be searchable across projects. 3. Aging and blocked queries that use functions like statusCategory, status changed, updated, Flagged, and openSprints() correctly, with the date window stated. 4. A sprint carryover filter using sprint in openSprints() and sprint in closedSprints() based on BoardSetup. 5. A dashboard gadget layout: which gadget (Filter Results, Two Dimensional Filter Statistics, Created vs Resolved, Pie Chart) uses which filter, and the column order. 6. Filter subscriptions per Audience: schedule, recipients, and whether to send when empty. 7. Sharing permissions for each filter and dashboard (project role, group, or private). 8. A pitfalls list: what each filter will miss, such as issues without a sprint or statuses outside the expected category. Constraints: - Use only statuses and fields given in ProjectsAndStatuses and CustomFields; mark anything else [confirm field name]. - Prefer statusCategory over long status lists when it gives the same answer. - Plain admin tone. No em dashes.