powerbi load JIRA worklog via RESTAPI so slow

hi, v-kelly-msft 

I had the same feeling about performance bottleneck you mention above, which is API call per row,  And it is testified by the fact  data will be loaded fast if  #"Invoked Custom Function1" line is removed.

What I am curious is that there is the same API call per row in https://community.powerbi.com/t5/Desktop/Get-data-from-Jira-Rest-API/td-p/516130, but seems fixed by changing from "each Json.Document(Web.Contents(#"AddIndex"{[Index]}[Custom]))" to "each Json.Document(Web.Contents([Custom]))".  That give me hope that maybe the poor performence is caused by some rule mentioned at this link, which is "avoiding loading table in power query"?

If the poor performance is caused by API call per row 100 percentage, then I don't know how to get worklog from JIRA quickly.  there are 3 potential approaches to get worklog data what I can find by now:

1. get whole worklog since date via https://jiradc.int.net.mycompany.com/rest/api/latest/worklog/updated?since=sometimestamp
2. get worklog one by one via "GET /rest/api/2/issue/{issueIdOrKey}/worklog/{id}"
3. get worklog for multi issues via eg. https://jiradc.int.net.mycompany.com/rest/api/latest/search?jql=issue%20in%20(ISSUE1, ISSUE2)&fields=worklog

BUT all above are not satisfied for me since

for 1: I don't want to hunt my interested data among whole company, it is too huge.

for 2：there are 4000 issues by now, one issue one api cal takes too much time.(the current problem we mentioned here)

for 3: was thought excellent, but sadly, the max count of worklog return per issue is 20, but of course there are plenty of issues whose count of worklogs excced.

I am tortured by this for 3 days!