No, your customer does not want to "fetch the data from the database". This is the worst possible way to report on Jira data and you should be telling them that their solution is utterly wrong.
Jira's database is not a proper database. It uses a database as a data store and it is not built for anything other than being a data store.
Simple example - look at an issue. You get a load of data from fields which looks simple in itself. That was probably 40 joins in the database (it's a minimum of 17 last time I looked, and can easily be hundreds). Simple JQL queries "translated" into SQL can go from one intuitive clause to SQL that needs multiple joins.
Get your customer to define their reporting properly and see if you can do it in Jira or with an App. If you can't, then look at getting the reporting add-ons that understand the Jira database in full (i.e. EasyBI or Dataplane) or add-ons that connect directly to other reporting tools. If they can't do the reports, then you will need to find or write something that uses the REST interface.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.