I think this would be an easy one, but I cannot seem to figure it out. Here is my situation I frequently create sandboxes especially of JIRA to test things prior to production deployment. In doing this, I make a mirror of the production system, and in doing this it creates all the application links. If I remove them on the sandbox it wipes them out the reciprocal link on all the other servers so Confluence, and especially Fisheye/Crucible stop working as they are no longer linked to production JIRA.
As a work around I just go in and disable outgoing and incoming authentication. But I would rather just get rid of it without touching the reciprocal link, is there a setting or a way to do that. (Note: I could just shut down eth0 and do it from the console, and when it tried to remove reciprocal it cannot as there is no network, but don;t like that solution either) I would prefer there just be some sort of checkbox or something that says don't touch the reciprocal.
Anyhow thanks in advance for any insight!
This happened to one of the JIRA instances that I support and all hell breaks loose (imagine more than 1,200~ active projects depending on it and the integrated features suddenly went missing). I have not remembered to ask Atlassian about it though, thanks for reminding me If the community can't help or provide insights, let's take it to Atlassian.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs