Is it recommended to span an epic over more than one release? I have epics that contain stories some of them cannot make it into one release. Should I create a new epic for those and assign the new epic to the new release?
Unfortunately this does not help: if I have an epic with a story that goes into release N and another story that goes into N+1 and I assign the epic to both releases then there is no way for me to rank the epic so it satisfies priorities in the two releases.
My question was a general one: is it a good practice to have epics that span two releases or the guideline is to restrict an epic to a single release?
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