You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
As @Tim Keyes shares in his new article Jira Align and Jira Integration: Jira Management Shared Sprints and Origin Sprints:
The Jira Align 10.61 Release provided an updated user interface for Jira Align Admin > Jira Management that includes an option for Jira sprints to sync with the options of "only sprints created on board" and "sprints created and shared to board".
In four years implementing AglieCraft/Jira Align I have not once encountered a valid use case for allowing the second option ("sprints created and shared to board"), which is the same as Origin Sprints being toggled off in versions prior to 10.61.
In fact, the Origin Sprint functionality was created specifically due to all of the corrupted data issues we ran into when implementing AgileCraft with Jira when boards were sharing sprints.
My question to the community is, for those who have actually implemented AgileCraft/Jira Align, do any of you NOT enforce origin sprints (aka "only sprints created on board") and if so, why?
While I appreciate speculative answers, they are fairly irrelevant unless you have experience with the connector and its behavior with both options. That is why I'm asking for real life examples from people using Jira Align integrated with Jira.
I have actually encountered this recently with a customer. I have two use cases to which I can speak.
1. The sprints were originally created on a different board (not shared) and the team moved boards. They brought their sprints with them to the new board. When we went to sync the sprints, we had only sprints created from that board turned on so they didn't wind up coming over via the connector. We had to turn this off to allow them to come over and then set it back to only sprints created by that board.
2. There were boards being integrated that were sharing sprints. They adjusted their practice to correct this going forward but still wanted to bring in historical data. We had to change the option to bring in shared sprints and then change back to only sprints created by that board.