Skip to main content

Jira Integration

PLANNED FEATURE

This integration is planned for a future release. The functionality described below is not yet available.

Currently, only the Xurrent integration is fully implemented and operational. For information about the available integration, please refer to the Xurrent integration documentation.

This guide covers the planned integration between Tripl-i and Atlassian Jira, which will enable automatic issue creation from discoveries, linking configuration items to issues, and tracking infrastructure changes through Jira workflows.

Overview​

The planned Tripl-i-Jira integration will provide:

  • Automatic Issue Creation - Create Jira issues from discovered problems
  • CI Linking - Link configuration items to Jira issues
  • Bidirectional Updates - Sync status between platforms
  • Custom Field Mapping - Map Tripl-i data to Jira fields
  • Workflow Automation - Trigger actions based on issue transitions

Architecture​

The integration architecture will consist of:

  • Tripl-i Components:

    • Discovery Engine
    • Event Manager
    • AI Analysis
    • CMDB

  • Integration Layer:

    • Jira Connector
    • Field Mapper
    • Webhook Handler
    • Queue Manager

  • Jira Components:

    • Issues
    • Projects
    • Workflows
    • Custom Fields

Installation​

When available, the installation process will include:

1. Install Tripl-i App for Jira​

For Jira Cloud:

  1. Navigate to Jira Settings > Apps > Find new apps
  2. Search for "Tripl-i Integration"
  3. Click Install
  4. Grant required permissions

For Jira Server/Data Center:

  1. Download the app from Atlassian Marketplace
  2. Navigate to Jira Administration > Add-ons > Manage add-ons
  3. Upload the application file
  4. Configure the app settings

2. Configure API Access​

You'll be able to configure API access through the Tripl-i admin interface by providing:

  • Your Jira instance URL (e.g., https://company.atlassian.net)
  • Integration username
  • API token (generated from Jira Profile > Security > API tokens)
  • Project key for issue tracking

3. Set Up Webhooks​

The integration will support webhook configuration for real-time updates:

  • Event subscriptions (issue created, updated, deleted)
  • Comment notifications
  • Project-specific filters
  • Bidirectional synchronization

Configuration​

Connection Settings​

The integration will support comprehensive configuration options:

Authentication:

  • API token-based authentication
  • OAuth 2.0 support
  • Secure credential storage

Project Mappings:

  • Map Tripl-i discovery types to Jira projects
  • Configure issue type mappings (incidents, problems, changes, vulnerabilities)
  • Custom field mapping support

Synchronization Settings:

  • Automatic issue creation from discoveries
  • Configurable sync intervals
  • Batch processing options
  • Webhook-based real-time updates

Field Mapping Configuration​

The integration will support flexible field mapping:

Tripl-i to Jira Mappings:

  • Title → Summary
  • Description → Description
  • Severity → Priority (with configurable mapping)
  • Affected CIs → Custom field or labels
  • AI Analysis → Custom field
  • Discovery Date → Custom field

Jira to Tripl-i Mappings:

  • Status → Event status
  • Resolution → Resolution status
  • Assignee → Assigned user
  • Updated date → Last sync timestamp

Issue Creation​

Automatic Issue Creation​

When implemented, the integration will automatically create Jira issues when:

  • Critical vulnerabilities are discovered
  • Performance issues are detected
  • Configuration drift is identified
  • Security events are triggered
  • Custom rule conditions are met

Issue Content​

Auto-created issues will include:

  • Descriptive summary and title
  • Detailed description with technical information
  • Affected configuration items (as links or custom fields)
  • AI analysis and recommendations
  • Severity/priority mapping
  • Discovery metadata and timestamps

Issue Templates​

The integration will support customizable templates for different issue types:

  • Vulnerability Issues: CVE details, CVSS scores, affected systems
  • Performance Issues: Metrics, thresholds, historical trends
  • Configuration Issues: Drift detection, compliance violations
  • Security Events: IOC information, threat intelligence

Webhook Integration​

Jira to Tripl-i Webhooks​

The integration will process webhook events from Jira:

  • Issue created, updated, or deleted
  • Status changes and workflow transitions
  • Comments and work log updates
  • Resolution changes

Tripl-i to Jira Webhooks​

Tripl-i will send webhook notifications to Jira for:

  • New discoveries requiring tickets
  • CI updates affecting existing issues
  • Status changes in linked events
  • Resolution confirmations

Automation Rules​

The integration will support automated workflows:

Trigger Conditions:

  • CI field updates
  • Status transitions
  • Custom field changes
  • Issue type modifications

Automated Actions:

  • Update Tripl-i event status
  • Link related CIs
  • Add comments with latest analysis
  • Trigger impact assessments
  • Update custom fields

Reporting and Dashboards​

Jira Dashboard Integration​

When available, custom gadgets will provide:

  • Discovery statistics
  • Resolution metrics
  • AI-powered insights
  • Trend analysis charts
  • SLA compliance tracking

JQL Extensions​

Custom JQL functions for advanced queries:

  • Find issues with active Tripl-i alerts
  • Filter by affected CI
  • Query by discovery type
  • Search by AI recommendations

Best Practices​

When the integration becomes available, follow these best practices:

1. Issue Management​

  • Use consistent naming conventions
  • Set up appropriate issue type mappings
  • Configure workflows that match your processes
  • Define clear resolution criteria

2. Performance​

  • Batch issue operations when possible
  • Use JQL efficiently for queries
  • Cache frequently accessed data
  • Monitor API rate limits

3. Security​

  • Use API tokens instead of passwords
  • Restrict integration user permissions appropriately
  • Audit integration activities regularly
  • Review and rotate credentials periodically

4. Data Quality​

  • Validate data before creating issues
  • Handle special characters properly
  • Maintain field mapping documentation
  • Review and update mappings regularly

Troubleshooting​

Common Integration Issues​

Authentication Errors:

  • Symptom: "401 Unauthorized" responses
  • Potential Causes: Invalid API token, expired credentials, insufficient permissions
  • Resolution Steps: Verify token validity, check user permissions, regenerate credentials if needed

Field Mapping Errors:

  • Symptom: "Field cannot be set" errors
  • Potential Causes: Missing custom field, incorrect field type, screen configuration issues
  • Resolution Steps: Verify custom field exists, check field permissions, review screen configurations

Webhook Failures:

  • Symptom: Webhooks not triggering
  • Potential Causes: Incorrect URL, network issues, webhook filters
  • Resolution Steps: Verify webhook URL accessibility, check filters, review Jira webhook logs

Performance Issues:

  • Symptom: Slow issue creation or updates
  • Potential Causes: Large batch sizes, network latency, rate limiting
  • Resolution Steps: Implement request batching, use async processing, optimize queries

Support and Feedback​

For questions or to express interest in this integration:

Note: This document describes a planned feature. Implementation timeline and final feature set may vary. Check with your account representative for the latest information about integration availability.