Unanswered

Atlassian Jira 'Get list of issues' - Where to specify JQL !?

(5) Share

Report

Posted on by dvm3

I am attempting to get issues out of Jira according to a JQL query. That is exactly what the official Jira connector is supposed to do according to its documentation: https://learn.microsoft.com/en-gb/connectors/jira/#get-list-of-issues-(preview)

However, there is literally nowhere to specify the JQL in the Power Automate step !? I feel like I'm taking crazy pills here ... can't find much on the web about this either. The step does execute, however it just returns the first page of 100 issues out of over 200,000.

Ideas ???

Categories:

Using connectors

I have the same question (0)

All responses (6)

Answers (0)

Talha_Dar 870 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @dvm3,

Each API response returns a distinct set of results, typically limited to 100 per page. To retrieve additional results, you can consult the API documentation for instructions on how to navigate to the next page and retrieve the next set of 100 results.

https://developer.atlassian.com/server/confluence/pagination-in-the-rest-api/

If you found my answer helpful, please consider giving it a thumbs-up or a like. Your feedback is greatly appreciated!
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
dvm3 18 on at

Like (3)

Report
Copy link

Link copied!

My beef is that the particular step indicates that it returns a set of results based on a JQL filter. However this seems to either just not be the case or I am missing something ? I understand pagination, I just refuse to believe I must page over 200,000 records (which are very verbose) to then wittle it down to the sub 100 I am interested in.

Is there any way to reach the creator's of the Jira plugins at MS I wonder ?

Was this reply helpful? Yes No
Talha_Dar 870 Super User 2024 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Considering the API limitation, it appears that seeking assistance from the creators may not be helpful. Instead, it would be advisable to explore and implement a suitable workaround to address this issue.

a workaround has been shared by @abm , which has also been approved by the owner of the post. To view the details, you can visit the following URL.

https://powerusers.microsoft.com/t5/Building-Flows/GET-Restful-API-Loop-through-requests-More-than-100-Jira-issues/m-p/912236/highlight/true#M128301

If you found my answer helpful, please consider giving it a thumbs-up or a like. Your feedback is greatly appreciated!
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
af5 4 on at

Like (0)

Report
Copy link

Link copied!

Hello @dvm3 ,

Did you achieve to extend the limit of the first 100 issues returned by the "Get a list of issues" action in Power Automate ?
Im also struggling to get all issues (> 1900) from this action.

Thank you for your return.

Was this reply helpful? Yes No
dvm3 18 on at

Like (1)

Report
Copy link

Link copied!
@af5... I moved away from using that (imo) mislabelled action and instead use a vanilla http API call: https://<company>.atlassian.net/rest/api/3/search

We're calling that API with the body below in a loop to take care of the pagination:
{ "expand": [ "names" ], "jql": "project = 'Project Name Here' AND updated >= -@{variables('JiraSearchUpdatedDaysAgo')}d AND created > '2023-03-1' OR (project = 'Project Name Here' AND status = ACTIVE)", "fieldsByKeys": false, "fields": [ "summary", "status", "created", "updated", "customfield_10485", "customfield_10590", "customfield_10589", "customfield_10487", "customfield_10488", "customfield_10489", "customfield_10597" ], "startAt": @{variables('StartAtIndex')} }

Hopefully that is helpful ... I can provide more pieces if needed.

Was this reply helpful? Yes No
AdyG 50 on at

Like (0)

Report
Copy link

Link copied!

Please use this action:

Was this reply helpful? Yes No