We want to be able to pull the JIRA requests into a SQL database to display requests for Managers and what is in their current queue. What is the best way to do that?
Welcome to the Community!
You can't use SQL on a Cloud system, so there's actually no question here.
Even if you could, the Jira database is simply not intended for reporting, and reading it with SQL is the very worst possible way to do any reporting on Jira data.
The best thing you can do is build your reports in a Jira dashboard, or use its dashboard reporting functions in Confluence (Jira dashboards are great for people familiar with Jira and not wanting any extraneous stuff around their charts, but Confluence pages are better for management reporting, as you can include brief explanations and detail ad-hoc rather than ask non-Jira users to have to understand exactly how Jira works)
There are other options - reporting apps can extend the Jira dashboards, give you more reporting (both inside Jira and in Confluence) and some can provide their own separate dashboarding functions!
Hi,
As mentioned already, users do not have access to the Jira Cloud database. I can suggest trying out the eazyBI app for Jira. It provides the flexibility to cover most of your reporting needs without direct access to the Jira database.
Kindly,
Janis, eazyBI support
Hi @Jeremy Doyle - Did you ever get this solved?
"reading it with SQL is the very worst possible way to do any reporting on Jira data"This is simply not true. When using BI analytics tools (like MS PowerBI) it is very useful and easy to export data from databases. We are currently joining data from several systems databases to create cross-system reports. With your current cloud "solution" there is almost no way to gain full access to OUR OWN DATA (which is usually accessible via the DB).How will we be able to track activity on a granular level? (like: userX created itemY in locationZ; userA updated itemB in locationC; ...)
I'm afraid it is absolutely true.
Please re-read the third line in my answer there, but I should have emphasised the last words as "Jira data".
BI analytics tools are great, when they are pointed at databases that are built for reporting, or have well-defined data dictionaries written by people who thoroughly understand the database they are looking at.
MS PowerBI pointed at an Atlassian database will fail, and fail hard. It's an absolute truth that it's the worst possible way to do it. Because the database is utterly unsuitable for reporting, and you don't understand it, so you won't be able to build a decent dictionary, or maintain it on every change (potentially as frequently as every 6 weeks)
To use your examples:
Thanks for your answer. In the end I don't care whether it is "good way" to do sth. or not. People get tasks (like: creating a metrics dashboard) which need to be completed. (Although I agree that optimizing the solution is always/often the right way to go.)
So, if you recommend to not use the database (which is as of now available AND stores the required information), how to approach the mentioned scenario? Especially when using the cloud version of Jira, since there is no DB access.
Events of each user and the affected/related item, including it's path, have to be recorded. The "location" was meant as the path (e.g., space->epic->task).
Example:
User: Bob
Event: created
Item: subtask
Location/Path: spaceA.epicB.taskC
This seems like bulldozing get people to use easyBI. I have built a very robust reporting mechanism off of jira data by studying the schema including epic level progress, efforts, sprint metrics etc. with precision. It is possible. Atlassian shouldnt turn into Apple.
It looks like you're new here. Sign in or register to get started.
