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
Next: Root
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'm getting this warning on an issue, but I've triple-checked the currently assigned team member is in the plan and he actually has other issues assigned to him within the same team. Nothing seems different between this issue and others without the warning.
Is there any way to debug Portfolio's errors/warnings, and understand what it's "thinking" is causing the error/warning?
Hi, Kirk! How are you!
I believe we will any a further investigation on this case so I've opened a ticket for you with our support team. Please access your email account in order to check the ticket URL.
When we find the root cause of that behavior, I'll post it here.
Kind regards,
JOÃO NUNES
Jira Support Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a resolution to this? This suddenly started happening yesterday for us
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can this be because of the config parameter Config → Scheduling → Issue assignee import level ?
I had this issue but once I put it to Sub-Task it all gone.
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.