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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello, as I mentioned in the title, we have updated our workspace id.
After the update, we also renewed our integrations. We can also see our new id in bitbucket. But in some integrations, our old id appears. This causes confusion. How can we fix this?
Is there another place we should change? I want to know if this is a general problem.
Unfortunately this is really reliant on the app developer to not use/store names of workspaces or to have a mechanism to update those.
Is there a particular integration that you noticed this on?
Yes, I understand you are right, we actually noticed this error in the marker.io bitbucket integration. But in our ongoing tests today, we noticed that they actually use the connected username, not the workspace id. And when we removed our other integrations and reconnected, the workspace ids were updated. So our problem is solved, thank you.
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.