Search

Categories
 BigPicture Enterprise

About BigPicture Enterprise

Differences between BigPicture Enterprise and BigPicture

 BigPicture Enterprise release notes

The root page DOCUMENTATION:BigPicture Enterprise release notes could not be found in space Documentation.

 BigPicture

About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Progress Tracking

Tutorials and tips

Integrations

 BigPicture 7.10 and earlier

Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects


 BigPicture release notes

BigPicture Cloud Backlog

 BigGantt

About BigGantt

BigGantt installation and updates

Cloud vs. Server - Key Differences in BigPicture on These Platforms

 BigGantt release notes

Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 Trello

 BigPicture Enterprise
 Jira Cloud

The root page DOCUMENTATION:BigPicture Enterprise Jira Cloud release notes could not be found in space Documentation.

 Jira Server

The root page DOCUMENTATION:BigPicture Enterprise Jira Server release notes could not be found in space Documentation.

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Trust Center

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »


Configuring Teams

The teams' assignment can be bi-directionally synchronized with Jira. The synched field can be added to you Jira issue screens and edited directly from there, indicating which team is assigned to the currently viewed or edited issue.

Team assignment can be synced with any custom field of the following type: 

  • "Labels" type
  • "Select list (single choice)" type.

When using labels the app can automatically generate a team label when a Team is assigned to a task but you can assign Team manually by creating label which must include the 'team#' prefix before the Team code.

In the case of select fields, you are required to predefine the select options using the Team codes.

Field data migration

When a different field than currently used is selected the option to migrate data will appear below the filed picker:

The data migration of a particular issue can fail in the following cases:

  • when migrating from a single select field to labels field: team code contains whitespaces;
  • when migrating to a single select field: a field does not contain the team code in the list of select options (the app does not create the select options during the migration process).  

The data migration is performed in the background and thus the user might not be aware of that process. Depending on the number of issues requiring an update it might take a significant amount of time.




  • No labels