Hi everyone,
I'm curious how teams here are managing workflows that involve both Product Information Management (PIM) and Jira.
For example, when a product needs to be created or updated, there can be several activities involved:
Product data enrichment
Content and copy review
Image or media approval
Translation
Technical data verification
Compliance checks
Final approval before publishing
Jira is often already being used to assign and track this work, while the actual product information lives in a PIM.
I'm interested in how others are connecting these two systems.
Do you create Jira issues directly from PIM workflows?
Do you sync product status or attributes between Jira and the PIM?
Are you using Jira Automation, REST APIs, webhooks, or an Atlassian Marketplace app?
How do you avoid duplicating the actual product data inside Jira?
Has anyone connected an open-source PIM with Jira or Jira Service Management?
I'm particularly interested in real-world implementations and what has worked well or not worked well for your teams.
Would be great to hear how you're approaching PIM and Jira integration.
Community moderators have prevented the ability to post new answers.
Hi! Welcome to the Atlassian Community.
The cleanest approach I’ve seen is to keep the PIM as the source of truth for product data and use Jira only for the work around that data.
A common pattern is:
PIM triggers Jira through a webhook or REST API
Jira creates/updates the work item for review, translation, approval, etc.
Only a few reference fields are synced, such as product ID, current status, owner, or a link back to the PIM
Jira Automation can then handle assignments, approvals, notifications, and transitions
I would avoid copying the full product dataset into Jira. Usually a unique product identifier plus a link to the PIM is enough.
For status sync, I’d also keep it fairly limited. For example, Jira can send back milestones like Approved, Rejected, or Ready to Publish, while the detailed product lifecycle stays in the PIM.
For a first implementation, I’d probably start with:
PIM webhook → Jira REST API → Jira Automation
and only introduce a Marketplace app or middleware if the integration becomes more complex.
The main design decision is really: which system owns each piece of data? Once that is clear, the integration tends to stay much simpler.
Hi @Booking Commerce !
I agree, keeping the PIM as the source of truth and using Jira for the work around it makes sense. The part worth solving on the Jira side is the process itself, because the same sequence repeats for every product.
Enrichment, copy review, media approval, translation, technical verification, compliance, final approval. That is a recurring process with a different owner at almost every step. Subtasks could handle it, but they multiply fast and you will end up with a dozen work items per SKU that clutter your board and reports.
For recurring processes like this, we keep the steps inside the work item as a checklist. For that, we use our solution, Smart Checklist for Jira. You can save the step-by-step instructions for each stage as a reusable checklist template and apply it automatically based on your own conditions - for example, to every work item of the Product Update type. Here's an example:
Each checklist item can have its own assignee, due date, and priority. So the copywriter, the translator, and the compliance reviewer all see their part in one ticket.
I hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.