Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,360
Community Members
 
Community Events
185
Community Groups

Even though I changed the Workspace name and id, the old workspace id appears in the integrations.

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.

 

1 answer

1 accepted

1 vote
Answer accepted
seanaty
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 06, 2022

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.

Like seanaty likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events