Share your experiences with JIRA Federation

[Stefan Broda]

Thousands of Atlassian customers run more than one JIRA instance in their organization. This is one of the reasons why in the JIRA State of the Union 2012, Federation was mentioned as a key part of the JIRA product strategy!

In line with that announcement, we have released the Federating JIRA Enterprise Guide to centralize best practices in administering, managing and running JIRA federations.

Do you run multiple JIRAs in your organization?

Which reasons to federate were most relevant to you?

How do you connect them? Application links? Any custom interfaces you developed?

Looking forward to comments, shared best practices and also questions!

[Sergio Freire - Xblend]

Hi, unfortunately I don't have access to the mentioned link @Stefan Broda  :(

Can you or anyone from Atlassian please review the permissions on the page?

[Daniel Borcherding]

We are federting for perfmance reasons and feel that it is an incredibly lack luster solution.

It seems like an "Unlimited" license should cover functionality up to and including a Single monolithic Jira instnace.

[Devu Heda]

Fedreation,

Issue linking and common dashboarding is great but what we want to see is

1. Issue searching (JQL) - Searching issues from the comfort of my exising instance
2. Issue creation - creating issues in the other system

Is there any possibility of this?

[Sergio Freire - Xblend]

Unfortunately, it doesn't seem so, as of Jira 8.4.

[M]

We have an internal and external Jira.

One for employees and one for partners.

The partners could be devs or customers

We currently have no connection but need it!