Product and support plan in Jira. Developers work in Azure DevOps. Every status update is copied by hand, or not at all, and someone spends Friday afternoon reconciling the two.
First: what the official integration does
Atlassian's Azure DevOps for Jira (Official) app brings development activity into Jira: branches, commits, pull requests, builds and deployments linked by issue key. That's very useful for traceability.
What it doesn't do is sync work items. A Jira issue and an ADO work item stay two separate records with separate statuses, comments and fields.
Your options for work item sync
- Manual updates. Free, error-prone, and the first thing to slip in a busy sprint.
- Scripts or Power Automate flows with webhooks. Flexible, but you own field mapping, loops (A updates B updates A), retries and errors.
- A sync app. Several Marketplace apps do this, including ours (Azure DevOps for Jira by Move Work Forward). Compare them on direction control, field mapping, conflict handling and how easy it is to see what failed.
How a two-way sync is set up (example with our app)
- Choose the direction first: Jira to ADO, ADO to Jira, or both. Decide carefully, because the direction can't be changed later and each direction needs different token scopes.
- Map types and fields per direction. Use "Mirror this mapping" to pre-fill the reverse direction, then review it.
- Map statuses with value mappings. Several ADO states can map to one Jira status.
- Decide on comments and attachments. Each is a toggle. Attachments sync up to 25 MB per file (ADO Cloud), and deleting an attachment on one side doesn't remove it on the other.
- Map users if you want assignees to carry over. This is optional.
Conflicts: if both sides change the same field, the latest change wins, per field, and the app prevents update loops.
When something doesn't sync: check the Audit log tab (Jira admin > Azure DevOps > Work Items Sync). Each sync attempt is recorded with its outcome and, for failures, a readable reason, so admins can often fix mapping problems themselves.
Tips from setups we've seen
- Start with one project and one work item type, and expand once mappings are right.
- Agree on which tool "owns" each field. Two-way sync works best when people don't edit the same field in both places.
- Keep the official app for development activity if you like it; work item sync is a separate concern.
How does your team split work between Jira and ADO?
Further reading: Two-way work item synchronization, How to sync work items