Categories

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

Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects


BigPicture Cloud Backlog

About BigGantt

BigGantt installation and updates

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

Shortcuts

Knowledge Base

Tutorials and tips

Trust Center

LINKS

Product Training

Success Stories

Partnership Program

SoftwarePlant's website

Atlassian Marketplace

Contact Support

BigPicture 8 is here!

Discover the landmark edition of the Atlassian Marketplace top-selling app! The new version is available to all Cloud, Server and Data Center users. Visit BigPicture 8 Documentation to learn more about it.



Auto-configuration

Auto-configuration option automatically configures the scope synchronization of newly added and existing but not configured Time-boxes.

Auto-configuration can take place once one of the following actions is performed:

  1. a new Box is created,
  2. a new team is allocated to a Box,
  3. a Box sync field is updated and a user saves settings (using scope synchronization templates),
  4. a Box sync mode is updated and a user saves settings (using scope synchronization templates)
  5. an auto-configuration option is selected and a user saves settings (using scope synchronization templates).

The app configures scope synchronization of Boxes within a particular Box type based on:

  • selected Box synchronization mode,
  • type of Box synchronized field.

Please note that in Jira, Sprints can be created only within boards.

Hence, when the "Sprint" field is used to synchronize Time-box scope, a respective Jira board is required to make the auto-configuration process work.

Auto-configuration of different Box sync modes and types of sync fields

Detailed rules of auto-configuration are described in the table below:

Field typeShared modeTeam specific mode

Sprint


    1. App creates a single new Jira Sprint and maps it to the Time-box (all teams and unassigned row)

    2. Sprint is generated within a "default Jira board" based on settings for a Box type.

      If Jira board is not specified, a system does not create Sprint during the auto-configuration process and leaves scope sync mapping empty.

    3. Pattern name: $BoxName
  1. App creates multiple new Jira Sprints maps them to different Time-boxes and teams accordingly.
  2. Sprints are generated:
    1. (for teams) within Team's Jira board selected in Administration - Global teams or Program Teams.

    2. (for "unassigned row") within "default Jira board" selected

      If some Jira board is not specified, a system does not create Sprint during the auto-configuration process and leaves a respective scope sync mapping empty.

  3. Pattern name: $BoxId Team $TeamCode

String

(Text field - single line)

    1. App creates a new value for a synchronized field and maps it to all teams and backlog of a Box.
    2. Pattern name: $BoxId
  1. App creates multiple values for synchronized field and maps them to different Teams and unassigned row.
  2. Pattern name: $BoxId Team $TeamCode

Select 

(Single list - single choice)

Not supported field type at the moment

Not supported field type at the moment