Jira API / Storage

I have a simple Forge app for Jira Cloud that calls the /rest/api/3/project endpoint to get back the project data for my Jira site. I would like to view this data in Tableau, using their OData connector. My plan is to insert the project data I’ve got into an external database (currently running on localhost). Then, create an odata API (using the simple-odata-server package) which Tableau will then use to retrieve the data.

Before I go further I wanted to check if there is a better way to do this, because it seems like a lot of work and I don’t think this would scale very well. I think I need my own server/database because Tableau requires an OData URL and I can’t get this from Jira. So I’m not sure if there is away around this duplicate storage of data but I would love to be wrong. Any comments/suggestions are greatly appreciated!

[deleted]

@JacksonDunn,

Have you seen Atlassian Analytics?

You’ve already anticipated my biggest concerns about scale and performance. Jira’s pagination and rate limiting might not work the way Tableau’s web data connector expects, especially at scale.

More than than, I think you’ll also find it a bit awkward to work with Jira’s data structures from JSON as if they were tables. You’d have a lot of things keyed to Jira’s way of unique identification (like “customfield_10201” instead of “my custom field name”), that can feel obscure in a relational model.

There are good reason we built the Analytics feature, which can be summed up to say, it’s not a trivial effort.

1 Like