Generate a status rollup comment for any JIRA issue based on all child issues and a given date range
Generates comprehensive JIRA status rollups by analyzing child issues and activity within a date range.
/plugin marketplace add openshift-eng/ai-helpers/plugin install jira@ai-helpersissue-id [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]jira:status-rollup
/jira:status-rollup issue-id [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]
The jira:status-rollup command generates a comprehensive status rollup for any JIRA issue (Feature, Epic, Story, etc.) by recursively analyzing all child issues and their activity within a specified date range. The command intelligently extracts insights from changelogs and comments to create a concise, well-formatted status summary that can be reviewed and refined before being posted to Jira.
This command is particularly useful for:
Key capabilities:
[Extended thinking: This command takes any JIRA issue ID (Feature, Epic, Story, etc.) and optional date range, recursively collects all descendant issues, analyzes their changes and comments within the date range, and generates a concise status summary rolled up to the parent issue level. The summary is presented to the user for review and refinement before being posted as a comment.]
The command executes the following workflow:
Parse Arguments and Validate
Issue Validation
mcp__atlassian__jira_get_issue to fetch the issueData Collection - Build Issue Hierarchy
parent = {issue-id}mcp__atlassian__jira_batch_get_changelogs for all issue keysexpand=renderedFields, filter by date range/tmp/jira-rollup-{issue-id}-{timestamp}.mdData Analysis - Derive Status
Generate Status Summary
h2. Status Rollup From: {start-date} to {end-date}
*Overall Status:* [Clear statement about health and progress]
*This Week:*
* Completed:
*# [ISSUE-ID] - [Specific achievement from comments]
*# [ISSUE-ID] - [Specific achievement from comments]
* In Progress:
*# [ISSUE-ID] - [Current state and specific details]
* Blocked:
*# [ISSUE-ID] - [Specific reason for blocker]
*Next Week:*
* [Planned item based on analysis]
*Metrics:* X/Y issues complete (Z%)
*# syntax for nested bullets (Jira wiki markup)Present to User for Review
Iterative Refinement
Post Comment to Issue
mcp__atlassian__jira_add_comment to post to parent issue/jira:status-rollup {issue-id} --start-date {date} --end-date {date}"Temp File Cleanup
/tmp/jira-rollup-{issue-id}-{timestamp}.mdError Handling:
Performance Considerations:
/tmp/jira-rollup-{issue-id}-{timestamp}.md containing:
Generate status for a Feature for a specific week:
/jira:status-rollup FEATURE-123 --start-date 2025-01-06 --end-date 2025-01-13
Output: Weekly status comment posted to FEATURE-123
Generate status for an Epic:
/jira:status-rollup EPIC-456 --start-date 2025-01-06 --end-date 2025-01-13
Output: Epic status summary with all child stories analyzed
Generate status for a Story with subtasks:
/jira:status-rollup STORY-789
Output: Status from story creation date to today
Generate status from a start date to now:
/jira:status-rollup CNTRLPLANE-1234 --start-date 2025-01-06
Output: Status from Jan 6 to today
Example Output:
h2. Weekly Status: 2025-01-06 to 2025-01-13
*Overall Status:* Feature is on track. Core authentication work completed this week with 2 PRs merged. UI integration starting with design approved.
*This Week:*
* Completed:
*# AUTH-101 - OAuth2 implementation (PR #456 merged, all review feedback addressed)
*# AUTH-102 - OAuth2 token validation (unit tests added, edge cases handled)
* In Progress:
*# UI-201 - Login UI components (design review completed, implementing responsive layout for mobile)
*# AUTH-103 - Session handling (refactoring cookie storage mechanism, PR in draft)
* Blocked:
*# AUTH-104 - Azure AD integration (blocked on subscription approval, escalated to infrastructure team). Per Jane Doe: "Need Azure subscription approved before proceeding - submitted ticket #12345"
*Next Week:*
* Complete session handling refactor (AUTH-103) and submit for review
* Finish login UI responsive implementation (UI-201) once design assets are finalized
* Begin end-to-end testing (AUTH-107) if session handling is merged
*Metrics:* 8/15 issues complete (53%)
š¤ Generated with [Claude Code](https://claude.com/claude-code) via `/jira:status-rollup FEATURE-123 --start-date 2025-01-06 --end-date 2025-01-13`
issue-id (required): The JIRA issue ID to analyze (e.g., FEATURE-123, EPIC-456, STORY-789, CNTRLPLANE-1234)--start-date (optional): Start date in YYYY-MM-DD format. Defaults to issue creation date if not provided--end-date (optional): End date in YYYY-MM-DD format. Defaults to today if not provided