Teams based on Jira teams
Initial setup
Setup must done by a Jira admin.
Configuration is done once for the entire instance.
In the Teams module:
Go to App Configuration > Integrations
Navigate to the Jira Teams tab
Generate an API token and add it to BigPicture
Log in to Atlassian account.
Click Create API token.
In the dialog that appears, enter a memorable Label for your token and click Create.
Click Copy to clipboard.
Add it to BigPicture
Enter the Organization ID
Open URL https://admin.atlassian.com
If you have access to more than one Organization, select the one associated with your BigPicture instance
The ID can be found in the URL
https://admin.atlassian.com/o/my-organization-id-xxxxx-xxxxxxx-xxxxxx/overviewCopy the ID from the URL and paste it into the required field
Enter the e-mail address
Click Save
You will see a confirmation message:
Organization ID is listed on the page:
Expiration of tokens
Jira tokens are valid for a limited period of time. To ensure that synchronization can continue, the token must be replaced periodically.
What happens if synchronization fails? (e.g., if the token stops working)
Changes made to Jira teams can no longer be transferred to BigPicture.
Teams that already exist in BigPicture remain unchanged (in the state corresponding to the last successful synchronization).
Will replacing the token with a new one trigger another synchronization?
No. Currently, synchronization is always triggered manually. There is no auto-synchronization
Create BigPicture teams based on Jira teams
In the Teams module:
Click the + button.
Select Create new team based on Jira team
Select a Jira Cloud team and fill out the fields:
Jira cloud team (required)
Team name (required)
Team code and color (required)
Board (optional)
Start date of Team memberships (required)
Click Create.
Result: A new team appears on the list.
Memberships
By default, the availability of team members is set to 100%.
Memberships of team members and their availability can be modified as usual.
When synchronization is triggered, based on a Jira team, new team members are added in BigPicture:
the date of adding a person becomes the membership start date
availability is set to 100%
When synchronization is triggered, based on a Jira team, team members are removed from BigPicture.
Using the same Jira team in multiple boxes
You can’t create multiple box teams based on the same Jira team:
You can assign the same BigPicture team to multiple boxes.
Can I synchronize an existing BigPicture team with a Jira team?
No. The old team needs to be removed and a new team (based on a Jira team) needs to be created).
Synchronization
Synchronization of BigPicture teams with Jira teams has to be triggered manually.
Synchronization is uni-directional. Information from Jira is pulled into BigPicture.
Where can synchronization be triggered
Synchronization must be triggered in the primary box of a team.
You can’t trigger synchronization in boxes that have inherited the team.
Global synchronization
All box BigPicture teams (based on Jira teams) get synchronized.
Exception: If a team has been edited in BigPicture, for example, team members have been added or removed, the team will NOT be synchronized during global synchronization to prevent the loss of information.
A pencil icon appears to teams that are excluded from the global synchronization.
How to trigger a synchronization
In a Teams module of a box:
Click Synchronize
Select Synchronize with Jira Cloud Teams
Local synchronization (per team)
If a team has been edited in BigPicture, for example, team members have been added or removed, the team will NOT be synchronized during global synchronization to prevent the loss of information.
A pencil icon appears to teams that are excluded from the global synchronization.
How to trigger a synchronization
To synchronize such a team, click the re-synchronize button:
synchronization applies only to one team
changes made in BigPicture are overwritten with Jira team information