Showing feature request status in Salesforce when product uses JPD and engineering uses Azure DevOps

I recently wrote up how teams connect Jira Product Discovery to Salesforce on one side and Azure DevOps on the other. The part that stuck with me is how far a simple sales question has to travel. 

An AE wants to know if the feature their customer asked for has shipped. The request was logged in Salesforce. Product prioritized it in Jira Product Discovery (JPD), and engineering built it in Azure DevOps.  

Product copies the approved idea into Azure DevOps by hand: title, description, maybe acceptance criteria. From then on, the two drift apart. Engineers update status, add comments, and link work in their own tool, and it doesn't get reflected in JPD.  

So product opens Azure DevOps to check, sales pings product, and the roadmap stops matching what's shipping. 

JPD has a built-in Salesforce integration. Your team can paste a Salesforce record link into an idea and show fields from that record, such as account or opportunity details. That covers context flowing into product. It works one link at a time; it's read-only, and nothing flows back to Salesforce. 

Getting status back to Salesforce takes a build. That could be Flow or Apex calling Jira, Jira Automation calling Salesforce, MuleSoft, or a third-party connector. Whichever route you pick, the same decisions come up. 

Decide where each piece of data starts. Customer context starts in Salesforce, priority starts in JPD, and delivery status starts in Azure DevOps. Give every field one owner, so two systems never edit the same value. 

Check which JPD fields can actually move. Standard fields and custom scores like impact or effort are usually fine. Insights, views, and formula fields are harder, and formula fields don't come through the Jira API at all. If product prioritizes a formula field, find that out before anyone promises sales a view built on it. 

Keep it to one idea per epic. JPD doesn't carry the epic, feature, and story breakdown, so that split happens in Azure DevOps after the handoff. Mirroring the full hierarchy back into JPD or Salesforce adds a lot of work for very little that sales would use. 

Translate statuses for sales. "Ready for QA" means nothing to an AE. Agree on a short list they understand, such as requested, approved, in development, and released, and map everything else to it. 

Sort out access early. Product and engineering rarely hold admin rights in each other's tools, and some security policies block one system from signing into another directly. This comes up often enough that it belongs in the first planning conversation, before anyone has picked a tool. 

For anyone who's closed this loop: where does your sales team see feature request status today? On the Account, on the Opportunity, or somewhere else entirely?