Skip to main content

​
Jira Integration

SignalPilot integrates with Jira to bring deployment history, ticket context, and issue tracking into your data investigations. Correlate data changes with deployments and find related bug reports.

​
What Jira Integration Provides

Context TypeWhat You GetExample Use
Deployment HistoryRecent releases and changes”What deployed last week?”
Related TicketsIssues mentioning data or metrics”Any tickets about the orders table?”
Issue DetailsFull ticket context and comments”What does ticket DATA-123 say?”
Sprint ContextCurrent sprint and priorities”What data work is in flight?”

​
Setup

1

Generate API Token

  1. Go to id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token
  3. Name it “SignalPilot” and copy the token
2

Configure SignalPilot

Add to your signalpilot.config.json:
{
  "mcp_servers": {
    "jira": {
      "type": "jira",
      "url": "https://yourcompany.atlassian.net",
      "email": "${JIRA_EMAIL}",
      "api_token": "${JIRA_API_TOKEN}",
      "projects": ["DATA", "ANALYTICS", "ENG"]
    }
  }
}
Include the engineering project key (e.g., ENG) to capture deployments that might affect your data.
3

Verify Connection

In a SignalPilot notebook, test with: @jira recent DATA

​
Using Jira Context

​
Correlating with Deployments

When data changes unexpectedly, check what deployed: 
You: "Why did conversion drop 8% last week?"

SignalPilot: Checking Jira for recent deployments...

Found 3 relevant deployments:

1. ENG-1234: "Checkout flow redesign" (Deployed Tuesday)
   - Related: DATA-567 (tracking pixel migration)

2. ENG-1198: "A/B test framework update" (Deployed Monday)
   - Affected 15% of users in test group

Correlation: The checkout deployment (ENG-1234) coincides with your drop.
Search for known data problems: 
You: "Are there any known issues with the orders table?"

SignalPilot: Searching Jira for orders table issues...

Found DATA-432: "Duplicate orders in production" (In Progress)
- Root cause: migration script ran twice
- ETA: End of week
- Recommendation: Filter to orders after 2024-01-01

​
Understanding Change History

Trace when and why data definitions changed: 
You: "When did we change the MRR calculation?"

SignalPilot: Searching Jira for MRR calculation changes...

Found DATA-345: "Update MRR calculation to exclude credits" (2 months ago)
- Before: MRR = price × quantity
- After: MRR = (price × quantity) - credits
- Deployed: 2024-01-15

Note: If comparing MRR before/after 2024-01-15, the calculation differs.

​
Jira Commands

CommandDescription
@jira recent <project>Get recent tickets
@jira search <term>Search tickets for a term
@jira ticket <key>Get full ticket details
@jira deploymentsShow recent deployments
@jira sprintShow current sprint status

​
Best Practices

1

Use Consistent Labels

Label data-related tickets consistently (e.g., data, pipeline, metrics). This improves search relevance.
2

Link Related Issues

When a bug affects data, link it to the data ticket. SignalPilot follows these links to provide full context.
3

Document Deployments

Include deployment dates in ticket descriptions or comments. This helps correlate data changes with releases.

Slack Integration

Combine with Slack for discussion context

dbt Integration

Add data lineage to deployment context

Context Aggregation

How Jira fits into the MCP architecture