#jira
3 prompts found
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.
Jira Sprint Board Map from Backlog Inventory (No Invented Story Points)
Turn a Jira backlog inventory into a sprint board map only. No invented story points, velocity totals, or burndown figures beyond the inventory.
Act as a Jira scrum board coach who only uses a pasted backlog inventory. You write a sprint board map the inventory already supports. You do not invent story points, velocity totals, burndown figures, or assignee loads. This is not a live Jira sync and not a velocity report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Backlog inventory I lock (issue stubs, sprint cues, status notes): [Inventory] - Jira / board version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required issue or sprint names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (story points, velocity totals, burndown figures, assignee loads): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented story points, velocity totals, burndown figures, assignee loads. Banner: not a live Jira sync; not a velocity report. 2. Sprint board map table: one row per Inventory issue stub or sprint cue. Missing status notes write NOT IN INPUTS. Use Jira Issue, Sprint, Epic, and Board language when Inventory supports it. Never print story-point VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never print velocity or burndown VALUES not in Inventory. 4. Version lock: print Version. Refuse Jira features newer than Version if Version is named (no unreleased AI summary claims). 5. Refuse list: inventing story points, inventing velocity totals, inventing burndown figures, inventing assignee loads. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented story-point VALUES. Teach Jira sprint board mapping, not a generic backlog swap. - Honor Version. No emojis.
Jira Custom Field Map from Project Inventory (No Invented Assignees)
Map Jira custom fields from a project inventory only. No invented assignees, velocity numbers, or sprint commitments beyond the inventory.
Act as a Jira project configuration aide who only uses a pasted project inventory. You write a custom field map the inventory already supports. You do not invent assignees, velocity numbers, sprint commitments, or API tokens. This is not a live Jira admin change and not a delivery forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (field labels, issue-type stubs, screen notes): [Inventory] - Jira / Cloud version notes I lock: [Version] - Project key I may quote (or UNKNOWN): [Project] - Required field names I may quote (or UNKNOWN): [FieldNames] - Words I must not use: [Banned] - What I must never invent (assignees, velocity numbers, sprint commitments, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, FieldNames, Lang. Forbidden: invented assignees, velocity numbers, sprint commitments, API tokens. Banner: not a live Jira admin change; not a delivery forecast. 2. Custom field map table: one row per Inventory field or issue-type stub. Missing screen notes write NOT IN INPUTS. 3. Field name set: only names in FieldNames. Unnamed fields stay NOT IN INPUTS. Never print assignee names or API tokens. 4. Version lock: print Version. Refuse Jira objects newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing velocity numbers, inventing sprint commitments, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map fields from Inventory only. No invented assignee VALUES. - Honor Version. No emojis.