Which tables to use to get a story with story points?

[Manthan Patel]

I want to get the story points for a story, I cannot find it in the Issues table.  I read somewhere its in the customfieldsvalue table, but where is that table? I cannot see that when connecting jira data through odbc.. I am using the CData odbc connector.  Basically all I need is to be able to get a story and its story points for further analysis on data, but am not able to find which tables to use and how to link them.. Very confusing documentation.

[Nic Brough -Adaptavist-]

I would stop using this database connection and do it properly - use a REST call to get the issues.  That way you don't have to worry about the tables or how they are related to each other

[Manthan Patel]

Thanks for your reply.  I am more of a database guy, so not quite familiar using the API's developing some code and all.  So I am trying to use the third party connectors and fetch data.  Can you elaborate more on the REST call method or any other easier way for me to get this?

[Nic Brough -Adaptavist-]

Yeah, you need to stop thinking database with Atlassian products, they're simply not built for any form of reporting and you really don't want to be reading them.

Have a look at https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/ - start with a look at the "get issue" call - when you use that, you'll get all the fields from an issue without having to look in multiple places.

[Manthan Patel]

Ya I understand its not built for reporting, but there are certain things operations team need and if not available directly within the platform we have to find alternate ways to do such things. If inbuilt we had such flexible options to query and create customer reports/alerts it would help.  Anyways I will give the REST api thing a try. Also one other issue I faced while using the odbc connector is its giving me 'Too many requests' or 'Rate limit exceeded' error while fetching even a not so big amount of data! Any resolution for this? Thanks in advance.

[Nic Brough -Adaptavist-]

"but there are certain things operations team need and if not available directly within the platform"

That's actually my point.  The database is not intended for reporting, and the stuff your "operation team needs" is hard to extract from it.  In fact, there are things you see on-screen and in REST calls that are not in the database at all.  So it's absolutely the wrong way to look at Jira data.

If using the odbc connector is giving you rate limit errors, then that's another reason to stop doing it that way - it's not working.  It's probably doing a really bad thing like asking for an issue view as though it's done by a database table, which in fact means it could be making hundreds of calls just for one thing.