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,466,252
Community Members
 
Community Events
176
Community Groups

Pull Request URL Linked to Old On Prem JIRA Server after Syncing to JIRA Cloud

Hello,

We just synced JIRA Cloud to Bitbucket and the Pull Request URL's are still linked to the Old On Prem JIRA Server vs the Cloud issues.  Our migration from JIRA on prem to cloud was successful. 

How do I update the urls in Bitbucket to reflect the .atlassian.net issues vs on prem?

Confirmed in Atlassian Integrations that the correct Jira Site is synced .atlassian.net

Thank you for your help

1 answer

1 accepted

0 votes
Answer accepted
Syahrul Atlassian Team Jul 24, 2022

Hey @Herb Salgado 

G'day!

I believe you still have the old integration in your Bitbucket Workspace; hence it's still linked with your old Jira server. 

Can you navigate to the Workspace settingsInstalled Apps?

Search for Jira and click the ">" button to locate your old Jira URL, as an example screenshot below:

Screenshot 2022-07-25 at 1.39.17 PM.png

If the URL shows your Jira OnPrem URL, you can click Remove to remove the integration, which should unlink your old Jira server. Once removed, it should re-link the Jira Issue key with your Jira cloud.

Let me know how it goes.

Syahrul

Hello Syahrul,

Thank you for the response.

The URL shows the atlassian.net address not the OnPrem address.   Should I remove it anyway and reattach it and see if that works ?

Herb

(If I click on the eMLR-1973 link it brings up the OnPrem URL )

URL_OnPrem.png

Syahrul Atlassian Team Jul 26, 2022

Hi @Herb Salgado 

Thanks for the update.

I believe we need to investigate the issue further, and I have proceeded to raise a support ticket on your behalf. Please get back to me on the support portal. here 

Cheers,
Syahrul

Syahrul Atlassian Team Jul 28, 2022

Hi everyone,

As suggested by @Herb Salgado I'll share how the issue was resolved.

Currently, Bitbucket cloud establishes a link in the commit or PR by following the Links configured in the repository settings.

In this case, the repository that is affected still has its Jira server URL as a primary link so when Jira wanted to establish the link it uses the Jira server as the Primary link instead the newly added Jira cloud integration.

To fix this we'll need to remove the old Jira server link by deleting it at Repository settings > Links

Screenshot 2022-07-28 at 12.58.40 PM.png

Once the old Jira server link is remove it will automatically make the Jira cloud link as the primary link.

Cheers,
Syahrul

Thank you Syahrul

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events