The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

JMWE - Sending issues in batches using callRest function

Hugo Michelez
October 31, 2023

Hi all, 

 

I'm trying to create a post-function that posts all issues for which the status has changed to a dedicated endpoint on an hourly basis.

 

As such, I've created a Scheduled Action. 

Every hour, all issues matching the following JQL posted: project = MY_PROJECT and type in (Bug, Task, Review, Sub-task) AND status changed AFTER -1h

 

Here the post-function I have so far: 

{# Set the URL of the API endpoint #}
{% set url = "https://mycompany/endpoint" %},

{# Set the headers for the request, including the auth token #}
{% set headers = {
"Content-Type": "application/json",
"Authorization": "Token abcde"
} %}

{# Set the body of the request, using the issue data #} |
{% set body = {
"issue": issue
} %}

{# Make the POST request and store the response #}
{% set response = url | callRest( verb="POST", options = {headers : headers} , body=body) | dump(2) %}

 

However, I realized that the webhooks are sent individually (per updated issue), and not in batch. Is there a way to change this ?

 

Thanks in advance!

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
David Fischer
Community Champion
October 31, 2023

Hi @Hugo Michelez 

The workaround is to modify the jql selector to return just one issue (limit the result to one issue) and then, in the post function, use the searchIssues Nunjucks filter to run the same jql search to retrieve the whole list of issues. 

However, you'll need to limit the fields returned by the issue search, otherwise you'll run out of memory. 

Hugo Michelez
November 4, 2023

It works perfectly!

 

Thanks a lot, @David Fischer