Overview
Go beyond simple issue lookups. This agent analyzes your Jira data to answer complex questions like "Why is this feature delayed?" or "How did we solve a similar problem before?"
**Capabilities:**
- Identify blockers and dependencies across epics and sprints
- Analyze historical issues to surface patterns and past solutions
- Synthesize insights from comments, linked issues, and activity logs
- Calculate timeline impacts and project health metrics
- Surface relevant precedents from your team's institutional knowledge
[{"type": "user", "content": "Why is the checkout redesign feature delayed? The PM is asking for a status update."}, {"type": "thinking", "content": "Analyzing checkout redesign status...", "thinkingSteps": ["Finding checkout redesign epic and related issues...", "Analyzing blockers and dependencies...", "Reviewing recent comments and status changes...", "Calculating timeline impact..."]}, {"type": "assistant", "content": "I've analyzed the **Checkout Redesign** epic (SHOP-892) and found the root causes of the delay:\n\n## Primary Blockers\n\n| Issue | Blocker | Owner | Days Blocked |\n|-------|---------|-------|-------------|\n| SHOP-923 | Waiting on payment API v3 from Stripe | Backend Team | 12 days |\n| SHOP-941 | Security review pending | InfoSec | 8 days |\n| SHOP-956 | Design changes requested after user testing | UX Team | 5 days |\n\n## Timeline Impact\n\n- **Original Target:** January 15, 2026\n- **Current Projection:** February 3, 2026\n- **Delay:** ~3 weeks\n\n## Key Findings from Comments\n\n- Sarah (Dec 20): *\"Stripe confirmed API v3 will be ready by Jan 10\"*\n- Mike (Dec 28): *\"Security review scheduled for Jan 6\"*\n- Design iteration should complete by Jan 8 per Lisa's update\n\n**Bottom Line:** Once Stripe delivers the API (Jan 10), the remaining work is ~2 weeks. The critical path runs through the payment integration.\n\n<ENTITY_ANNOTATION id=\"SHOP-892\" title=\"Checkout Redesign Epic\" integrationType=\"JIRA\" />\n\n<CTA label=\"View Epic\" action=\"Open the Checkout Redesign epic in Jira\" />\n<CTA label=\"See All Blockers\" action=\"Show all blocking issues for this epic\" />"}, {"type": "user", "content": "Have we seen this payment API delay issue before? How did we handle it?"}, {"type": "thinking", "content": "Researching similar past issues...", "thinkingSteps": ["Searching historical issues involving payment API delays...", "Found 3 similar incidents in the past 18 months...", "Analyzing resolutions and workarounds used...", "Extracting lessons learned..."]}, {"type": "assistant", "content": "Yes, I found **3 similar incidents** where we were blocked on external payment API updates:\n\n## Historical Precedents\n\n| Issue | Date | Wait Time | Resolution |\n|-------|------|-----------|------------|\n| SHOP-412 | Mar 2025 | 18 days | Built mock API, parallelized work |\n| SHOP-234 | Aug 2024 | 9 days | Escalated to Stripe account manager |\n| PAY-89 | Feb 2024 | 21 days | Implemented feature flag, shipped partial |\n\n## What Worked Best\n\n**SHOP-412** had the most effective approach:\n1. Backend team created a mock API matching Stripe's spec\n2. Frontend and integration testing proceeded in parallel\n3. Final integration took only 2 days once real API arrived\n4. Net time saved: ~10 days\n\n**Recommendation:** Consider the mock API approach from SHOP-412. The team documented the pattern in their retro notes.\n\n*From SHOP-412 retro (Marcus, Mar 2025):* \"Mock API strategy should be our default playbook for external API dependencies. Added to team runbook.\"\n\n<ENTITY_ANNOTATION id=\"SHOP-412\" title=\"Payment Gateway v2 Integration\" integrationType=\"JIRA\" />\n\n<CTA label=\"View SHOP-412 Details\" action=\"Open SHOP-412 issue details\" />\n<CTA label=\"Open Team Runbook\" action=\"Open the team's API dependency runbook\" />"}]
