I set up the following scenario.
When Portfolio schedules the work. It set's it up for 2 releases. It adds 3 stories to the first sprint but is ignoring the 2nd sprint. The 4th story shows up in the first sprint of the 2nd release.
I want the 4th story to show up in the 2nd sprint of the first release. Is there any special configuration I need to do?
The setup you describe should work. I've tested out the scenario you described in my instance and Portfolio scheduled both sprints into the one release:
Could you please provide more specific detail for your setup so I can investigate why it's not working for you?
Also make sure that the difference in start/end dates for your release is equal or more than double your sprint length. My sprints are 2 weeks long so if I end the release 1 day short of 4 weeks then the sprint will be pushed to the next release (because Portfolio can't fit a full sprint into the release).
I have a board with releases that occur every 4 weeks. I then have a team set up with an iteration length or 2 weeks.
I went back to the dates and understand the issue. I have figured a way to resolve it, but think we can do a little better.
Here is my set up:
I resolved it by extending the release through Sunday. This fixes my scheduling issues.
I was thinking of controlling the dates via sprints, but i cannot set a date in the sprint until I start them.
Is there a way to tell Portfolio to ignore the weekends?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG