JCI Workflow Status Sync Limitation – Direct Status Field Synchronization Not Supported

Published Date: June 9, 2025

Validated: Yes

Audience: Everyone

Products and Versions Covered:

Jama Connect Interchange™ (JCI)
Jira Integration

Summary

Jama Connect Interchange™ (JCI) does not support direct synchronization of workflow-controlled Status fields between Jama Connect and Jira. Attempting to map Status fields on both sides can create workflow conflicts and lead to unintended state changes.

This article explains the limitations and provides a recommended pattern for safely reflecting status information between systems.

Resolution

Best Practice

Do not map workflow-controlled Status fields between Jama Connect and Jira. Instead, create read-only mirror fields in both systems and allow JCI to populate them. This preserves each system’s workflow integrity and prevents unintended status transitions.

Implementation

Step	Action	Detail
1	Add Mirror Fields	In Jama Connect, add a field such as “Jira Status (Text)”. In Jira, add “Jama Status (Text)”.
2	Map in JCI	Configure JCI field mappings: • Jira Status → Jama Status (Text) • Jama Status → Jira Status (Text)
3	Keep Original Status Read-Only	Do not map or expose native Status fields in JCI. Each system should manage its own workflow states independently.
4	Communicate Limitation	Inform stakeholders that direct Status synchronization is not supported and may introduce workflow conflicts. Mirror fields provide visibility without operational risk.
5	Track Demand	Log customer interest (e.g., Sim&Cure, Oceaneering, BioIntelliSense) under Jira epic CON-WFS-SYNC-IDEA for future prioritization.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.

Related to