JIRA DVCS connector issue

[MUSRepo]

I originally hooked up our Bitbucket repository to a test instance of JIRA but have since switched to our production instance. The links from Bitbucket to JIRA are still pointing to the test instance. Is there a way to force Bitbucket to point the links to the appropriate instance? I've removed the test JIRA instance from the Integrated Applications list.

[MUSRepo · Accepted solution]

Thank you for the response. By links I'm talking about the link from the Bitbucket repository activity stream to JIRA issues. I found what I was looking for under the Links section of the Repository Administration panel. Both the test and production JIRA instances were listed in the Configured Links section linking with the same issue types. Once I removed the Configured Link to my test instance, everything pointed correctly to my production JIRA install.

[MUSRepo]

See answer above.

[AgentSmith]

When you say links, I believe that consists of the navigation link in JIRA as well as the DVCS connection to the Bitbucket/Github repo(s). Both can be changed to suite your needs.

For the former, you can reference this document for more details:

https://confluence.atlassian.com/display/JIRA/Creating+Links+in+the+Application+Navigator

In terms of the DVCS connector, you can link to another Bitbucket or Github account by entering in the oauth id/secret key. You can have multiple DVCS connections to various Team or Individual accounts as well.

More on that here:

https://confluence.atlassian.com/display/AOD/Linking+a+Bitbucket+or+GitHub+repository+with+JIRA+OnDemand