Details
-
Epic
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Done
-
None
-
None
-
Business
-
Team synchronized with Jira group
-
Resources
-
BigPicture, BigPicture Enterprise
-
JIRA server, JIRA cloud
-
121
-
121
-
-
Done
-
-
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, Sprint 2022/13, Sprint 2022/14, Sprint 2022/15, Sprint 2022/16 SIW
-
PI2022/03
-
Yes
-
Killer feature
Description
Business case:
If you have already an existing team in Jira set as Jira group you can easily transfer it to BPE, so your Jira groups corresponds well with BPE Teams.
Creating a team based on existing Jira group follows much the same process as creating a new team in BP from scratch, except of selecting and adding members one by one. Instead of that, you can select the whole Jira group - members from that group will be added automatically to BPE Team. Team memberships will be by default set to the date of BP team creation, so the whole process is hassle free. You can edit it, if wished. If you make changes in Jira group members list, it can be quickly reflected in BPE by using the Synchronize button.
Thanks to creating teams based on Jira groups there is much less manual effort.
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.
1. Create team based on Jira group
- 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 cannot be made to teams created based on Jira groups:
- delete member
- Add member
- The Team can be created based on the Jira group in all box types incl. Root.
- The team created based on Jira group can be inherited to lower level boxes and can be promoted to higher level boxes.
- The team created based on Jira group and promoted to the higher level box can be sync only in the higher level box, where it belongs to.
- Only one team can be created based on one Jira group
2. Synchronize Teams created based on Jira groups
- changes made in Jira group (add/remove member) will be reflected in BP after synchronization (Button: Synchronize with Jira groups - after clicking the members list is updated)
- Synchronize with Jira Groups 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.
- only Jira groups that are not overwritten are synchronized