You might want to check to make sure that you have the "Stage sprint constraint" setting turned on, in your portfolio configuration. Under "Scheduling".
The stage spring constraint was turned off, but I turned it on and still have the same result. I've got this setup as a kanban style portfolio and a kanban team. Could that also be a contributing factor?
We are trying to avoid managing to the sprint level detail in Portfolio b/c of the volume of projects we have an the different variations of sprint length, etc. that we have too.
Any other ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apologies, that was the extent of my ability to assist. I also have my own problems with the scheduler inexplicably generating bizarre schedules for kanban teams that seem to have nothing to do with what I'm telling it to do. To the point where we can't use JIRA Portfolio at all. That's what brought me here in the first place.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.