---
title: "Jira Teams Sync, Multi-Instance Connections, and Resources View Customization"
canonical: "https://support.appfire.com/space/SUPPORT/3737682308/Jira%20Teams%20Sync%2C%20Multi-Instance%20Connections%2C%20and%20Resources%20View%20Customization"
format: markdown
---
# Jira Teams Sync, Multi-Instance Connections, and Resources View Customization

This article addresses multiple use cases related to BigPicture Enterprise on Jira Cloud, including synchronization limitations, multi-instance connection status, and timeline navigation in the Resources module.

## Summary

This article covers three distinct areas of BigPicture Enterprise functionality:

1. **Jira Teams Synchronization:** Current limitations on Jira Cloud due to platform API availability.
2. **Multi-Instance Connections:** Status of adding multiple URLs in the Enterprise version.
3. **Resources Module Navigation:** How to manage date ranges and view bi-weekly sprint data.

---

## Use Case 1: Jira Teams Synchronization on Cloud

### Problem/Context

Users may find that Jira Teams integration is unavailable or not syncing as expected in BigPicture Cloud.

### Cause

The Jira Teams integration is currently unavailable on Jira Cloud due to a platform limitation. The API previously used for this integration was part of the Connect platform. BigPicture has transitioned to Atlassian's **Forge** platform, where an equivalent API for Teams has not yet been made available by Atlassian.

### Solution/Workaround

This is an external limitation that requires an update from Atlassian.

- **Track Progress:** You can monitor and vote on the official Atlassian feature request here: [JRACLOUD-92072](https://jira.atlassian.com/browse/JRACLOUD-92072).
- **Impact:** Voting and commenting on the Atlassian ticket helps increase its priority on their development roadmap.

---

## Use Case 2: Adding Multiple URLs (Multi-Instance Connections)

### Problem/Context

Users attempting to establish new multi-instance connections in BigPicture Enterprise may find the option unavailable.

### Cause

Establishing new multi-instance connections is temporarily disabled while the integration undergoes essential platform and infrastructure updates.

### Solution/Workaround

- **Status:** The development team is actively working to restore this feature.
- **ETA:** There is currently no confirmed ETA for the restoration of new multi-instance connections.

---

## Use Case 3: Customizing the Resources Module View

### Problem/Context

Users want to set a specific end date for the Resources view or view data in bi-weekly increments to match two-week sprints.

### Solution/Workaround

#### Timeline Navigation

In the Resources module, timeline navigation is designed around an **anchor Start date**.

- **End Date:** You cannot manually specify an arbitrary end date. The end date and total span are dynamically determined by the selected **Time period**, **Zoom level**, and **Aggregation mode**.
- **Color Indicators:** In wider spans (Quarter/Half-year), capacity cells collapse into color status indicators (e.g., red for over-allocation). To see exact numbers, switch the aggregation to **Weekly** or **Monthly**.

#### Bi-Weekly / Sprint View

While there is no native "Bi-weekly" aggregation option in the Time Period selection, you can achieve this using **Timeboxes**:

1. Create **Timeboxes** that correspond to your 2-week sprint durations.
2. In the Resources module, set the **Aggregation** to **By timeboxes**.
3. This allows you to see workload and capacity specifically for each sprint period.

For more details, refer to the documentation on [Navigation and interface (Resources) - Aggregation by timeboxes](https://support.appfire.com/space/DLP/2211744025/Navigation+and+interface+%28Resources%29#Turn-on-the-aggregation-by-timeboxes).