jira
This skill provides expert guidance on managing Jira projects end-to-end, from structuring issues hierarchically to planning sprints based on team velocity. It covers workflow setup, JQL querying for reporting, and best practices for keeping backlogs groomed and teams aligned on deliverables.
Jira helps you manage projects, organize issues, plan sprints, and configure workflows for team collaboration.
AI-generated summary based on this skill's SKILL.md
Install
RightNow-AI/openfang/jira · repository language: Rust
git clone https://github.com/RightNow-AI/openfang
cp -r openfang/crates/openfang-skills/bundled/jira ~/.claude/skills/jiranpx skillfed install RightNow-AI/openfang/jiraFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I manage Jira projects effectively?
Jira helps you manage projects by organizing work into issues, epics, stories, and tasks within a hierarchical structure. Start by defining your project settings, creating a board (Scrum or Kanban), and establishing clear workflows that match your team's process. Use sprints for time-boxed delivery, maintain a groomed backlog with prioritized items, and track progress through velocity metrics. Jira's project management capabilities scale from small teams to enterprise deployments.
What are jira sprint planning best practices?
Jira sprint planning works best when you establish sprint goals upfront, estimate story points consistently, and involve the whole team in capacity planning. Review your team's historical velocity to set realistic sprint scope. Break down epics into smaller stories with clear acceptance criteria, link dependencies to surface blockers early, and use Jira's backlog view to prioritize and move items into sprints. Regular refinement sessions keep your backlog healthy and planning predictable.
How do I write good Jira issue descriptions?
Jira issue descriptions should be clear, concise, and actionable. Include context about what needs to be done and why, add acceptance criteria so the team knows when work is complete, and link related issues to show dependencies or relationships. Use Jira's formatting tools to structure information with headings and lists. Good descriptions reduce back-and-forth questions, speed up development, and make it easier for team members to pick up work during sprints.
What are JQL query examples for Jira reporting?
Jira Query Language (JQL) lets you filter issues for reporting and analysis. Common examples include: project = PROJ AND status = "In Progress" (current work), assignee = currentUser() AND resolution = Unresolved (my open issues), and created >= -7d (issues from the last week). Use JQL to build dashboards, run velocity reports, find blockers with issuelinks, or track technical debt by label. JQL is powerful for custom reporting beyond Jira's built-in gadgets.
How do I configure Jira workflows and automation?
Jira workflows define how issues move through states like To Do, In Progress, and Done. Configure workflows in project settings by adding transitions, conditions, and validators that match your team's process. Jira automation rules can trigger actions automatically—for example, moving an issue to Done when all subtasks complete, or notifying the team when a blocker is added. Automation reduces manual work and keeps your workflow consistent across the team.
How should I manage Jira blockers and dependencies?
Jira manages blockers and dependencies through issue linking. Use link types like "blocks," "is blocked by," and "relates to" to show relationships between issues. In your backlog and sprint views, linked issues help surface dependencies early so you can plan around them. Create blockers as separate issues when external factors delay work, assign them to the responsible party, and track resolution. Regular dependency reviews during sprint planning prevent surprises and keep teams unblocked.
SKILL.md
rendered from the published skill — quoted content, verbatim
Jira Project Management Expert
You are a Jira specialist. You help users manage projects, create and organize issues, plan sprints, configure workflows, and generate reports using Jira Cloud and Jira Data Center.
Key Principles
- Use structured issue types (Epic > Story > Task > Sub-task) to maintain a clear hierarchy.
- Write clear issue titles that describe the outcome, not the activity: "Users can reset their password via email" not "Implement password reset."
- Keep the backlog groomed — issues should have acceptance criteria, priority, and story points before entering a sprint.
- Use JQL (Jira Query Language) for powerful filtering and reporting.
Issue Management
- Every issue should have: a clear title, description with context, acceptance criteria, priority, and assignee.
- Use labels and components to categorize issues for filtering and reporting.
- Link related issues with appropriate link types: "blocks," "is blocked by," "relates to," "duplicates."
- Use Epics to group related stories into deliverable features.
- Attach relevant screenshots, logs, or
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
crates/openfang-skills/bundled/jira/SKILL.md