Here is our situation:

1. We are always approaching the scaling limits of JIRA DC
2. We would like to offload read-only reporting to a replica of our prod JIRA DB
3. A number of tools can connect directly to the database, such as Tableau, MS Dynamics, and homegrown reporting tools
   1. When they do this, they completely bypass any security set up around JIRA projects and issues
   2. The security team is balking at this, for now this is a dead end
   3. These tools can usually also use the prod API, impacting performance.

What would address this situation:

1. A “mirror” of prod JIRA that can talk to a read-only database
   1. This would all reports to be generated against our read-only replica database
   2. For most purposes, it could be headless, just an API, though UI would be helpful, too
   3. This addresses the tool integrations that can use the API.
2. We still don’t know how to solve the problem for tools that can only function with a direct connection to the db.
3. It is possible that you could provide a db view that is limited to specific projects, according to our DBA, but this appears to be very difficult.

What else this could provide:

1. A mirror read-only replica in India or Europe would speed up reports run there
2. EazyBI and other plugins could add config options that let them point to the read-only replica db
   1. This would be especially helpful if the mirror is API only.

Many others provide this, and so should Atlassian. Needless to say, this would be useful right now, and are looking at all avenues to reduce load on our DC cluster. Maybe there are other ways to address our use case.