🚀 SprintRecap: Jira Integration Setup Guide

Follow this step-by-step guide to connect your Jira instance with SprintRecap and start generating automated sprint reports in minutes.

Prerequisites

Before you begin, make sure you have:

  • Jira administrator access or permissions to generate API tokens
  • Your Jira instance URL (e.g., yourcompany.atlassian.net)
  • Active SprintRecap account
  • At least one active sprint in your Jira project
1
Generate Your Jira API Token

First, you'll need to create an API token in your Jira account. This token will allow SprintRecap to securely access your Jira data.

  1. Log in to your Atlassian account at id.atlassian.com
  2. Navigate to Security → API tokens
  3. Click "Create API token"
  4. Give your token a descriptive name like "SprintRecap Integration"
  5. Click "Create" and copy the generated token immediately

Screenshot placeholder:

Screenshot of Jira API token generation page
2
Connect Jira to SprintRecap

Now you'll connect your Jira instance to SprintRecap using the API token you just created.

  1. Log in to your SprintRecap dashboard
  2. Navigate to Settings → Integrations
  3. Click "Add Jira Integration"
  4. Enter your Jira instance URL (e.g., yourcompany.atlassian.net)
  5. Enter your Jira email address
  6. Paste the API token you generated in Step 1
  7. Click "Test Connection" to verify the setup
  8. If successful, click "Save Integration"

Screenshot placeholder:

Screenshot of SprintRecap Jira integration form
3
Load Your Jira Fields

SprintRecap needs to understand your Jira field configuration to generate accurate reports.

  1. In the integration settings, click "Load Jira Fields"
  2. Select the Jira project(s) you want to include in reports
  3. Wait for the field discovery process to complete
  4. Review the detected fields and their types
  5. Click "Confirm Field Mapping"
4
Set Your Sprint Field

Configure which field SprintRecap should use to identify sprint assignments.

  1. In the field mapping section, locate the "Sprint" field
  2. If using standard Jira, this is usually Sprint
  3. For custom configurations, select your sprint tracking field
  4. Verify the field shows active sprints in the preview
  5. Click "Set as Sprint Field"
5
Map Additional Custom Fields (Optional)

Enhance your reports by mapping custom fields for additional insights.

Recommended Mappings:

  • • Story Points → Effort estimation
  • • Epic Link → Epic grouping
  • • Priority → Task prioritization
  • • Labels → Categorization
  • • Components → Team/module tracking

Custom Fields:

  • • Business Value
  • • Risk Level
  • • Customer Impact
  • • Technical Debt
  • • Testing Requirements
  1. Review the list of available custom fields
  2. Select fields you want to include in reports
  3. Configure field aliases for better report readability
  4. Set up field value mappings if needed
  5. Save your custom field configuration
Final Check

Let's verify everything is working correctly before generating your first report.

Verification Checklist:

  • Jira connection is active and tested
  • Project fields have been loaded successfully
  • Sprint field is properly configured
  • Custom fields are mapped (if applicable)

Test your setup:

  1. Navigate to the Sprint Reports section
  2. Select an active or recently completed sprint
  3. Click "Generate Report"
  4. Verify that data appears correctly in all sections
📋
Sample Configuration JSON

Here's an example of what your final configuration might look like:

{
  "jira": {
    "baseUrl": "https://yourcompany.atlassian.net",
    "email": "your-email@company.com",
    "apiToken": "ATATT3xFfGF0...",
    "projects": ["PROJ", "TEAM"],
    "fieldMappings": {
      "sprint": "customfield_10020",
      "storyPoints": "customfield_10026",
      "epicLink": "customfield_10014",
      "priority": "priority",
      "labels": "labels",
      "components": "components"
    },
    "customFields": {
      "businessValue": "customfield_10100",
      "riskLevel": "customfield_10101",
      "customerImpact": "customfield_10102"
    }
  },
  "reportSettings": {
    "includeSubtasks": true,
    "excludeEpics": false,
    "timeZone": "America/New_York",
    "workingDays": ["monday", "tuesday", "wednesday", "thursday", "friday"]
  }
}
🔒
Security & Privacy

Data Security

  • • All API tokens are encrypted at rest
  • • Data transmission uses TLS 1.3
  • • No sensitive data is logged
  • • Regular security audits
  • • SOC 2 Type II compliant

Data Privacy

  • • Only project data is accessed
  • • No personal information stored
  • • GDPR compliant data handling
  • • Data retention policies enforced
  • • Right to data deletion
💬
Need Help?

If you encounter any issues during setup or have questions about SprintRecap, we're here to help!

📧 Email Support

Get help via email

💬 Live Chat

Chat with our team

📚 Knowledge Base

Browse help articles