You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am encountering a warning related to scheduling an item that is in the team's backlog when setting up a portfolio plan for the team. The error/warning reads
This issue can't be scheduled properly because the assigned team isn't present in your. Change the assigned team to one that's in your plan, or add the assigned team to your plan. Then, recalculate your plan
I look at the items in question and they have been defined to belong to the team in question. So what is the likely cause of this?
I have also checked of the dependencies and in the couple of instances I saw that the dependencies weren't targeted to the Releases I have included in the plan, however in the other cases the items had no dependencies to speak of yet the same warning. Of course I have items in the plan being scheduled without any errors/warnings and can't figure out what is so special about the few where this error/warning appears.
The issue is that Portfolio looks for teams that are defined in it's system.
You'll need to ensure that all of your teams are configured correctly and that all of the Stories (and their Sub-Tasks) are assigned properly.
This guide may be able to help you out:
Hope this helps,
That’s just it. I confirmed the configuration of the team and the sources for the portfolio plan. Since the warning is associated to some items I checked those items are associated to the team. If there are any dependencies across teams on the item then those teams have been included as needed.
As these things are resolved then not clear why the error.
It has been a while and if my memory serves me right the issue revolved around the the need to define Team in portfolio as a shared team. This said, the fact Jira doesn't have a native object definition of Team and it is first defined in Portfolio had something to do with it.
I am sorry I can't offer more clarity in this.