Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
The team says the Jira board is noisy and the velocity report does not match the number of completed items they see on the board. Draft a cleanup plan. Assume the user has not provided the board filter, workflow, status mapping, sprint settings, report settings, custom fields, permissions, or JQL.
Without the bundle
Clean up the board by removing old issues, closing done work, and standardizing statuses. Use JQL to find stale tickets and update the workflow so the velocity report is accurate. This is weak because it assumes the cause, does not request board/report settings, does not explain why board and report numbers can differ, and suggests live changes without confirmation.
Using the bundle
There is not enough evidence to decide what to change yet. Source note: Jira guidance should be checked against official Atlassian source categories for Jira Software Cloud boards/backlogs, workflows/transitions, JQL, reports, and permissions. Local evidence used: none. Missing before conclusion: board filter, project/space, board type, columns/status mapping, sprint and report settings, JQL, workflow transitions, resolution logic, custom fields, permissions, and example work items. Plan: 1. Capture read-only board evidence: board filter, columns, quick filters, swimlanes, visible work item examples, and permission scope. 2.
Why this is better: The bundle-assisted output is stronger because it asks for Jira source evidence, separates board/report/JQL scopes, avoids inventing the workflow or fields, and sets a confirmation boundary before live changes. No measured model evaluation was run for this example.
Inspect this example in the repositoryTool guide
Jira
Defines safe, source-aware use of Jira in OpenKnowledgeBank bundles.
Read the fileWorkflow
Plan Jira JQL and Report
Query-shape and source-check workflow for Jira JQL, reports, dashboards, and API-backed analysis.
Read the fileWorkflow
Review Jira Board and Backlog
Inspect-first workflow for Jira board, backlog, sprint, and workflow cleanup planning.
Read the fileTemplate
Jira Board Cleanup Plan
Output format for source-scoped Jira board, workflow, JQL, report, automation, or API cleanup planning.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Jira (Jira Software)
- Teams working in software, digital-products, technology
When to use it
- A proposed Jira (Jira Software) configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Plan Jira board, backlog, workflow, and report work without inventing local fields, statuses, filters, permissions, or issue data.
- Separate official Atlassian product behavior from user-provided Jira site evidence.
- Create source-scoped JQL, reporting, automation, and REST API plans with verification and confirmation boundaries.
- Reconcile board, report, JQL, and API differences by aligning scope, filters, permissions, time windows, and status logic.
What it helps produce
- Jira board cleanup plan
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Jira (Jira Software) and produce Jira board cleanup plan that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with atlassian.com — Software / Jira, then confirm that the reference is current and applicable. Inspect Jira before drafting.
Context path: bundles/tools/jira
What the bundle includes
Tools
- Jira
- Jira Software
- Jira Cloud
- JQL
- Jira Automation
- Jira Cloud REST API
Frameworks
- verify-first Jira evidence review
- board-report-query reconciliation
- workflow change confirmation boundary
Commands
/plan-jira-board-cleanup
Evaluations
- Jira planning quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Not a complete Jira administration, Data Center, pricing, plan, Marketplace app, Rovo, REST API, automation, or release-feature reference.
- Requires user-provided Jira site, space/project, board, workflow, field, permission, report, automation, and API evidence before final conclusions.
- Does not replace security, privacy, procurement, legal, compliance, administrator, scrum master, project manager, product owner, or engineering-lead review.
Safety notes
- Require explicit confirmation before creating, editing, transitioning, deleting, commenting on, exporting, bulk changing, or moving Jira work items; changing workflows, statuses, boards, filters, dashboards, permissions, automations, notifications, or API-connected actions.
- Do not claim access to Jira sites, projects/spaces, boards, workflows, work items/issues, reports, automations, users, groups, permissions, or API results unless the user provides evidence or authorized tool access.