Map Jira Delivery Fields in Productboard
Open the Jira integration’s Field mapping and syncing section, add compatible field pairs and choose their synchronization behavior. Save the mapping and test a deliberate field update.
Before you start: Use a Maker with Admin access. The documented field mapper requires an integration with one Jira project selected; inspect that project’s required fields first.
Worked example: Map Productboard Effort to Jira Story points for a linked sample Feature. A manual estimate of 5 should travel through the agreed direction without treating a parent rollup as a supported outgoing estimate.
Step-by-step guide
Inspect the integration scope
Open Settings → Integrations → Jira and choose the relevant connection. Verify it points at the intended single project and issue types.
Add a compatible pair
In Field mapping and syncing click + Add Mapping. Select the Productboard field and a Jira field of the matching type.
Choose the write behavior
Select Set once for push/link/import-time assignment, or two-way sync for later updates. Decide which system should author the value before enabling two-way behavior.
Satisfy required fields
Inspect the missing-required-fields banner and supply supported required mappings. Check that the chosen issue type can actually be created.
Save and exercise a change
Click Save Field Mapping. On a linked sample change the intended field, then inspect both sides. Merely enabling two-way sync does not trigger an initial update.
Common mistakes
Mapping incompatible field types
A Jira checkbox cannot be mapped to a dropdown. Choose compatible types instead of assuming matching names are sufficient.
Expecting rollup effort to write to Jira
Only manual Productboard effort values are documented as outgoing story-point values.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.