This article walks you through how to configure and understand the sync logic between Proggio and Jira.
If you are still not connected, check this article: Connecting Proggio with Jira.
Configure the Tickets You Want to Sync
Once connected to your Jira instance, you’ll be prompted to select which Jira tickets and issue types to sync with Proggio.
Proggio will import tasks (issues) and users according to your selection and visualize them on a timeline.
- Proggio’s patented “ProjectMap” structure organizes imported Jira data by workstreams. Learn more about workstreams here.
- Issues with dates will be placed on the timeline.
- Issues without dates will appear in the backlog.
Changes made in Proggio will sync to Jira instantly. Jira updates are synced into Proggio using the “Sync” button or automatically via the Proggio Jira Listener (if enabled).
Field & Status Matching
Once projects are selected, you’ll enter a configuration screen to match fields and statuses.
📌 Fixed Field Matching
Proggio map Jira fields (like “Summary”, “Assignee”, “Due Date”, or custom fields) to Proggio’s standardized fields.
- Mapping is done per Jira project and issue type.
- See below a table shows Proggio fields (left) and corresponding Jira fields (right).
📌 Value Matching
Jira status values (e.g., “To Do”, “In Progress”, “Done”) vary across projects. Proggio provides a value matching interface to align Jira statuses with its workflow logic.
- A table displays Proggio status categories and the mapped Jira status values.
- Each project can be customized separately.
- Helps Proggio interpret task status for timeline rendering, workstream segmentation, and reports.
📝 Best Practices
- Use consistent status schemes across Jira projects when possible.
- Review mappings regularly when adding new issue types or modifying workflows.
Sync Logic: How Data Flows Between Proggio and Jira
Proggio supports both manual and automatic sync with Jira. Here’s how synchronization works:
1. Automatic Sync via Jira Listener
- Enable the Proggio Jira Listener to automatically sync updates from Jira into Proggio.
- Listener tracks changes in real-time using Jira webhooks.
- New issues, updates, and status changes in Jira appear instantly in Proggio.
2. Manual Sync Options
| Action | How to Trigger |
|---|---|
| Sync All Projects | From PPM screen, click “Sync All Projects” |
| Sync Single Project | Inside a project, click “Sync Project Now” |
| Sync Single Issue | Inside issue view, click “Sync Issue Now” |
3. Timeline Logic
- Issues with dates: appear in the timeline.
- Issues without dates: stored in the backlog.
- Proggio assigns a default duration to undated tasks (configurable).
4. Subtasks and Hierarchy
- Proggio supports syncing Jira subtasks along with parent issues.
- Progress rolls up from subtasks to parent.
5. Status Filtering
- You can exclude certain Jira statuses from being imported (e.g., “Canceled”, “Closed”).
6. Bi-Directional Sync
- Yes (Default) – Changes in Proggio are pushed to Jira, and vice versa (via Listener or manual sync).
- You can deselect specific fields for one-way sync.
7. Time Tracking Support
- Enable Proggio’s built-in time tracking to visualize progress based on Jira time logs.
- Used for reporting actual vs. planned time per workstream.
8. Create & Delete Behavior
- Issue created/edited in Proggio: Synced back to Jira.
- Issue deleted in Proggio: Does not delete the issue in Jira.
- Issue deleted in Jira: Automatically removed from Proggio (if Listener is enabled).
9. UI Behavior
- Changes in Proggio highlight the sync icon.
- Sync runs in background; users can keep working.
- Notification confirms sync success and provides quick links to updated items.
Need help? Contact Proggio Support or your Customer Success Manager.
