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 have set my initiatives up in a separate project that I pull into multiple different Portfolio plans to represent cross-projects goal completion.
This has resulted in a "This issue can't be scheduled properly because the assigned team isn't present in your plan" error in some of my plans due to a previous team association i.e.
Can anyone advise on whether there is a way for an initiative to have two separate teams assigned to it in two separate plans?
Thanks for your reply!
Unfortunately, I'm not sure this will work as our structure requires multiple separate teams to work on the same initiative across multiple different departments.
I could assign everyone who will be working on an initiative to the same shared team, however, this will be counter-intuitive to the company structure.
Additionally, as individuals will not be working on initiatives at all (i.e. we are using them as placeholders of department goals for the quarter), and, as far as I understand, teams are assigned to issues so that Portfolio can assign appropriately, a shared team will likely not by-pass the error as it won't be the shared team working on the given plan's issues (it'll be that department./project team).
Thanks again for your help!
I see the same warning message: "This issue can't be scheduled properly because the assigned team isn't present in your plan" for some items in a plan related to a single team and in the simplest of cases - as in not looking to plan across an initiative that is shared by many teams and their plans.
When I review the items in question they are assigned to the Team and so the warning message appears to be a contradiction.
Then there is the irony of Team as a artifact in Jira. Atlassian company stock symbol is "Team" and yet this artifact in Jira isn't even a first class citizen. Its hidden in number of layers within Portfolio which just doesn't make sense. Soi much for "teaming"
Thanks for the reply, Tarang. I'm sorry that you're having the same issue.
Unfortunately, I have yet to receive an answer to my issue, however, on the level of a team that is not shared across projects, have you tried re-associating the teams set up in Portfolio with the Jira "Team" as per the attached.