The JIRA database is a data store. It's about as optimised for reporting as I am optimised for a trip to Mars without a spaceship or suit.To give you a rough idea, look at a single issue. If it's a bit complex, you may have to join up to 40 tables, often in joins 4 deep, and do them repeatedly, just to get the basic issue data.Whatever reporting you are trying to get to, please
That can be done inside JIRA far more easily than using SQL or reporting add-ons.
Go to Issues -> Search.
There is a simple search allowing you to define a search with drop-downs, but I prefer the advanced one where I can write "JQL". This is *not* SQL, but has some similarities. The main thing to understand about it if you are coming from a SQL background, is that is it only the "where" clause. It says nothing about output, it just gives you lists of issues that match criteria
Your select statement example is too vague to be turned into a proper query, but try something like "project = ABC" to see all the issues in that project, or "project = ABC and resolution = unresolved" to see the open ones, and so-on. See https://confluence.atlassian.com/jirasoftwareserver074/advanced-searching-921472935.html for a lot more...
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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