Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Samet Aydin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 6, 2022

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.
June 6, 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?

Samet Aydin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 6, 2022

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