# JIRA Sync Quality Checklist

## Purpose

Comprehensive validation of JIRA synchronization operations to ensure data integrity, format correctness, and three-way alignment between Git, BMAD, and JIRA systems.

## Required Artifacts

[[LLM: To execute this checklist, you need:

1. Recent sync operation output or report
2. Access to JIRA project (via MCP tools)
3. Git repository access
4. BMAD story/epic files
5. Configuration file: .bmad-workspace/ck-jira-integration/config/jira-expansion-config.yaml
   ]]

## Checklist Sections

### 1. Pre-Sync Validation (Basic Level)

[[LLM: Check these foundational items before any sync operation]]

- [ ] **Configuration Exists**: Verify jira-expansion-config.yaml is present
- [ ] **Project Key Valid**: Confirm JIRA project key is configured
- [ ] **Git Repositories Mapped**: At least one Git repository is configured
- [ ] **MCP Tools Available**: Atlassian MCP tools are accessible
- [ ] **Team Configuration**: Team members are configured (if using assignments)

**Rating**: ⭐⭐⭐⭐⭐ (5/5 required for basic sync)

### 2. Format Conversion Quality (Comprehensive Level)

[[LLM: Validate that all content is properly converted from Markdown to JIRA Wiki Markup]]

- [ ] **Headers Converted**: All `##` headers → `h2.` format
- [ ] **Lists Formatted**: Markdown bullets → JIRA bullets correctly
- [ ] **Code Blocks**: \`\`\`code\`\`\` → `{code}...{code}` blocks
- [ ] **Inline Code**: \`text\` → `{{text}}` conversion
- [ ] **Links Updated**: `[text](url)` → `[text|url]` format
- [ ] **Bold/Italic**: Proper conversion of text formatting
- [ ] **No Markdown Remnants**: Zero markdown syntax in final JIRA content

**Rating**:

- ⭐⭐⭐⭐⭐ Perfect conversion (ready for production)
- ⭐⭐⭐⭐ Minor formatting issues (acceptable)
- ⭐⭐⭐ Multiple issues (needs cleanup)
- ⭐⭐ Major problems (not ready)
- ⭐ Failed conversion (critical)

### 3. Three-Way Sync Accuracy (Expert Level)

[[LLM: Verify alignment between all three systems with specific metrics]]

#### Git Analysis

- [ ] **Commit Count Accurate**: Actual count, not placeholder
- [ ] **Author Attribution**: Git authors mapped to JIRA users
- [ ] **Time Range Correct**: Commits within specified period
- [ ] **Branch Coverage**: All configured branches analyzed

#### BMAD Alignment

- [ ] **Story Count Match**: All BMAD stories accounted for
- [ ] **Epic Structure**: Epic hierarchy preserved in JIRA
- [ ] **Metadata Sync**: Story metadata reflects in JIRA fields
- [ ] **Status Mapping**: BMAD status → JIRA status correct

#### JIRA Reflection

- [ ] **Issue Creation**: New stories created successfully
- [ ] **Updates Applied**: Modified stories updated
- [ ] **Links Functional**: All hyperlinks work correctly
- [ ] **Field Mapping**: Custom fields populated accurately

**Three-Way Health Score**: \_\_\_% (Calculate: matched items / total items × 100)

### 4. Data Integrity Validation

[[LLM: Deep validation of sync quality and completeness]]

- [ ] **No Data Loss**: All source data preserved
- [ ] **Bidirectional Sync**: Changes flow both directions
- [ ] **Conflict Resolution**: Conflicts handled appropriately
- [ ] **Audit Trail**: Sync operations logged with timestamps
- [ ] **Rollback Possible**: Can undo sync if needed

**Integrity Rating**:

- ✅ PASS: Full integrity maintained
- ⚠️ WARNING: Minor integrity concerns
- ❌ FAIL: Data integrity compromised

### 5. Performance & Scale Assessment

[[LLM: Evaluate sync performance for current and future needs]]

- [ ] **Sync Duration**: Completed within reasonable time
- [ ] **Resource Usage**: No excessive API calls or timeouts
- [ ] **Batch Efficiency**: Bulk operations used where appropriate
- [ ] **Error Handling**: Failures handled gracefully
- [ ] **Scale Ready**: Can handle 10x current volume

**Performance Grade**: A+ | A | B | C | D | F

### 6. User Experience Validation

[[LLM: Assess the quality of user-facing aspects]]

- [ ] **Preview Accuracy**: Preview matches final result
- [ ] **Progress Feedback**: Clear status during operation
- [ ] **Error Messages**: Helpful guidance on failures
- [ ] **Success Confirmation**: Clear completion message
- [ ] **Next Steps**: Guidance on what to do next

**UX Quality**: Excellent | Good | Acceptable | Poor

## Overall Sync Quality Assessment

[[LLM: Synthesize all sections into final assessment]]

### Summary Scores

- Basic Validation: \_\_\_/5 stars
- Format Quality: \_\_\_/5 stars
- Three-Way Accuracy: \_\_\_% health score
- Data Integrity: PASS/WARNING/FAIL
- Performance: \_\_\_ grade
- User Experience: \_\_\_ rating

### Ready for Production?

- [ ] ✅ **READY**: All criteria met, sync is production-quality
- [ ] ⚠️ **CONDITIONAL**: Minor issues to address first
- [ ] ❌ **NOT READY**: Significant issues requiring resolution

### Improvement Recommendations

[[LLM: Based on the validation results, provide specific recommendations:

1. Highest priority fixes needed
2. Quality improvements suggested
3. Performance optimizations available
4. Process enhancements recommended
   ]]

### Next Steps

[[LLM: Guide the user on immediate actions:

- If READY: Proceed with confidence
- If CONDITIONAL: Address specific items
- If NOT READY: Run validation again after fixes
  ]]

---

_This checklist ensures production-quality JIRA synchronization with comprehensive validation at multiple levels._