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've defined a new shared teams in Portfolio and confirmed the changes commit
Portfolio states that one of the teams was updated and then gets stucked. Only reboot can release the situaition
What can be the reason?
I cant say anything definitively without more details but on the surface since this is coming from commits relating to changes with teams, I would guess that its not a Portfolio specific error but rather something User directory related or hanging trying to communicate with the user directories, like a possible external directory timeout occuring while portfolio is attempting to commit the change for the user associations.
I would suggest checking the logging first to see if there are any explicit errors during the commit that can help narrow this down.
Let us know what you find.
The logs are huge, we can't find nothing 100% related and we're still digging into it.
I might forgot to specify something which could be important, we're not opened to the internet and our JIRA & Protfolio installed locally on our servers. We have to download each plugin/add-on specifcally and installed it locally.