I have been reviewing Portfolio for JIRA for some time and all times I have run in to a problem I have found a solution, almost always caused by myself.
However since a few days something strange have appeared. It seems like the automatic scheduling have stopped working. In my backlog I have many issues and some of them refuses to get scheduled.
The only hint for these issues under scheduling factors are:
This issue is not appearing in the schedule. This may be because:
Recalculating the plan does not help (tried numerous times)
If I add a story via portfolio, the scheduler will schedule the issue in the plan. However once the change is comitted to Jira the scheduling of the issue disappeares again. The issue is still visible in the scope, but the item disappears from the scheduled plan.
My plan consist of three boards, one team for each board. One of the issues I have problem scheduling only appears on one board. In portfolio the issue is assigned to one team, but does not get scheduled when I use the team filter for that team (however it appears in scope list).. but when I include another team as well the the issue get scheduled (for the correct team).
Another strange behaviour is that if I assign the issue to team 1 (correct team) and then reassign it to Team 1 and then back to Team 1 the scheduler will assign dates as they should. When I after that commit the changes to Jira, the issue looses its scheduling again.
First of all, I'm sorry that you've been frustrated!
What do each of your board filters look like? Issues can 'disappear' from Portfolio if they no longer match the board filter that's associated with your plan, which I suspect is the issue here.
After you commit, do you see any kind of message along the lines of 'these issues will no longer be visible in Portfolio?'
And can you confirm if you can still see the issue in the scope table, just not the schedule? Or you can't see the issue anywhere at all in Portfolio anymore?
It seems like when I changed changed the team issue source to the correct board most of the issues got scheduled correct.
This was not an obvious solution to me, but seems to work.
I do still have problems with some issues connected to a specific release. The issues connected to the release does not get scheduled at all, but if I remove the release tag they get scheduled as expected.
Any ideas why issues marked with a specific release would not get scheduled?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs