What is the best approach on a new release plan to add the intermediate maintenance sprint that the same team is doing on the former major versions ? It's the same team, they alternate several maintenance sprints, one per major version and other pure development sprints for the new release.
So far, I'm thinking to get the maintenance sprint as Epic/Issues and assign the full team on it in order to generate some alert on the capacity. But I'm curious to see if anyone solved this problem already.
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events