Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple Parents and Data Limiting

rvermette
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 20, 2022

Ok, so for the dashboard I'm building in google sheets with the "Jira for Google Sheets" extension, I need to pull a lot of data on subtasks, as well as their parent tickets. 

Using the standard extension method, I can pull all the subtasks in a single pull because their descriptions all start with the same line. So I can just pull any ticket that matches that condition and I'm set.

Where things get complicated is in pulling the relevant data from their parents. Those have no unique identifying marker I can use, so as far as I can tell that means I'd have to do individual queries for each individual one. I know this can be done with the =Jira() command directly in a cell, but the problem I then run into is that I have to do hundreds of these, which immediately fall apart due to rate limiting. This is the message I get in every cell: "User is rate limited, please try again after some time." 

I've tried looking up a way to remove this limit online, but so far have had no luck. Does anyone know how that might be accomplished? Or alternatively, another way to get to this data?

1 answer

1 vote
Hannes Obweger - JXL for Jira
Atlassian Partner
April 20, 2022

Hi @rvermette

welcome to the community!

Independently of the Google Sheets extension, loading the parent tasks for a known set of children is always tricky in Jira; JQL just doesn't support this very well.

One thing you could consider is to use one of the hierarchy-focused apps in the Atlassian Marketplace, let them build the issue hierarchy, and - if still needed - export data from there.

Just to play this through for the app that my team is working on, JXL for Jira:

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing and inline-editing any issue field, plus it supports various kinds of issue hierarchies. So what you could do is:

  • Define a JQL statement that includes all your relevant sub-tasks and any possible parent issues (e.g. all stories of your project) - if there are additional issues in the result set that aren't actually parent issues, you can filter them out later within JXL, no problem.
  • Let JXL sort out the issue hierarchies across your issues. This is a one-click operation.
  • If still needed, export to Excel via the built-in export function.

This is how step 2 looks in action:

hierarchy.gif

As said, I can only speak for JXL, but there's other apps in the Marketplace that can do similar things. I'd recommend trying some (there's always a 1 month free trial, and some apps may be free forever) and see which one works best for you.

Hope this helps,

Best,

Hannes | https://jxl.app

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events