Details
-
Epic
-
Status: In Progress (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
Business
-
Team synchronized with Jira group
-
Resources
-
To do
-
BigPicture Enterprise
-
JIRA server, JIRA cloud
-
113
-
113
-
-
-
Sprint 2019/13, Sprint 2021/29, Sprint 2022/01 SIW, Sprint 2022/02, Sprint 2022/03, Sprint 2022/04, Sprint 2022/05, Sprint 2022/06 SIW, Sprint 2022/07, Sprint 2022/08, Sprint 2022/09, Sprint 2022/010, Sprint 2022/011 SIW, Sprint 2022/12
-
PI2022/03
-
Yes
Description
Before change:
User is allowed to create Teams only by adding team members one-by-one.
After change:
User is allowed to add Team based on the Jira group of users and re-synchronize it later on if needed. If Jira group does not exist anymore, Team is deleted in BigPicture during re-synchronization.
- Data gained from Jira groups once the team was created based on the Jira group:
- Team name
- Members
- Data in BP fields:
- Team name = Jira group name
- team code - needs to be entered by the user when creating a team in BP
- Team membership start date - by default is set for 'Now'() can be edited by the user. When adding a member as a result of later sychronization, the 'Now' () date from the time of synchronization will be set
- Membership availability - by default set to 100%
- The following changes made in BP make the Team status to be changed from 'synced' to 'overwritten':
- Team name change
- Delete member
- Add member
- The Team can be created based on the Jira group in all box types incl. Root.
- Only one team can be created based on one Jira group
- Synchronize with JiraGroups on a Box should only synchronize Teams from that box. It does not synchronize teams created on the basis of Jira Groups in descendants' boxes. Team changes caused by parent synchronization are visible in children where this team is allocated.
- Scheduled Synchronization is added to periodically synchronize existing teams in the system.
- Sync is one side Jira -> BP, changes made in BP will not apply in Jira
