Two-Way Jira Integration Release#
Delivered: June 7, 2024 (First Friday of June)Overview#
Enable seamless bidirectional synchronization between Jira and Shorter Loop:Push work items from Shorter Loop to Jira
Import Jira tickets into Shorter Loop
Maintain project consistency during transition periods
Key Features#
Flexible Adoption Paths#
Teams can choose their integration approach:Full migration: Import all Jira issues at once
Phased adoption: Start with a small team evaluation
Continuous sync: Maintain parallel workflows during transition
Integration Methods#
1.
Two-Way Sync (recommended)
Setup Guide#
Prerequisites#
Jira account with GLOBAL ADMINISTER permission
API token with 12-month expiration (default is 7 days)
Connection Process#
1.
Navigate to: Integrations → Apps → Link from Jira
Jira Hostname (e.g., yourcompany.atlassian.net)
2.
All Jira projects import automatically after linking
Projects remain inactive until connected to teams
3.
Each Jira project connects to exactly one Shorter Loop team
Three-step configuration:2.
Choose work-item types to sync
Technical Implementation#
Smart Synchronization#
shorterloopId field automatically created in Jira:Company-managed projects: Auto-provisioned
Team-managed projects: Requires manual addition
Prevents duplicates through ID matching
Webhook Management#
Created automatically upon team-project connection
Removed when disconnecting
Data Handling#
Clears all Jira metadata from Shorter Loop items
Removes project connections
Automatically disconnects associated Jira project
Test Cases#
| Category | Key Verification Points |
|---|
| Connection | Token validation, Project import |
| Synchronization | Bidirectional item creation/updates |
| Field Mapping | Data consistency across systems |
| Error Handling | Token expiration, Permission issues |
| Cleanup | Webhook removal, Data sanitization |
Best Practices#
1.
Set API tokens to 12-month expiration
2.
For team-managed projects:Manually add shorterloopId field to all work types
Verify field presence before sync
3.
Monitor sync status during initial adoption
4.
Use CSV import for historical data migration
Modified at 2025-06-11 02:01:37
