/
Linking two Jira Cloud instances with BigPicture

Linking two Jira Cloud instances with BigPicture

Summary: This article explains the supported architecture and configuration for linking two separate Jira Cloud instances, both running BigPicture Enterprise, to achieve a consolidated portfolio view and bidirectional synchronization.

Environment:

  • Product: BigPicture / BigPicture Enterprise

  • Platform: Jira Cloud

  • Configuration: Multi-instance setup (two instances both with Enterprise licenses)

Problem:
Organizations running multi-Jira Cloud setups often need to consolidate portfolio views across different instances while keeping mapped fields (such as dates, status, and custom fields) synchronized. Users need to know if a "dual-primary" or cross-connection scenario is supported where both instances act as primary for each other.

Cause:
By default, BigPicture documentation typically covers a "Primary Enterprise + Additional Standard Jira" setup. Users with Enterprise licenses on both instances require confirmation on whether they can establish a reciprocal connection.

Solution/Workaround:

Parallel Cross-Connection (Dual-Primary)

It is supported to connect two Jira Cloud instances in parallel where both have BigPicture Enterprise installed. This allows both instances to act as "primary" for each other, enabling consolidated views on both sides.

Configuration Steps:

  1. Generate API Tokens: Create two separate Jira API tokens (one for each instance) to facilitate the connection.

  2. Establish Connection A to B: On Instance A, go to BigPicture App Configuration and add Instance B as an "Additional Jira Instance" using the API token.

  3. Establish Connection B to A: On Instance B, repeat the process to add Instance A as an "Additional Jira Instance."

  4. Field Mapping: Configure field mappings on both sides to ensure consistent data synchronization for dates, status, and other custom fields.

  5. Box Configuration: You can create identical Boxes on both instances that include projects from both Jira A and Jira B.

Key Requirements & Behavior:

  • License Matching: To ensure all features work as expected in both directions, both instances must have the same license level (BigPicture Enterprise).

  • Bidirectional Sync: Field synchronization is fully bidirectional. Changes made in Jira B are reflected in BigPicture on Jira A (and written back to Jira B), and vice versa.

  • Functional Parity: There are no reported functional limitations or errors when connecting two Enterprise instances compared to the standard "Enterprise to Standard" setup.