Forums

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

JIRA webhook sends entire issue comment history. Any way to filter that out on the JIRA side?

wesfalc March 2, 2018

I am currently working on developing a JIRA integration with another ticketing system and I am exploring JIRA webhooks (https://developer.atlassian.com/server/jira/platform/webhooks/) to do the same. I only subscribe to two webhook events - issue_created and issue_updated.

The integration works fine but the problem I observe is that the webhooks framework sends the entire comment history of the JIRA issue whenever the issue is updated. This is regardless of whether a new comment was made on the ticket or not.

In the JSON payload sent by JIRA, under issue -> fields -> comments, all comments on the issue are listed. In our usage of JIRA for this integration, it is quite likely that the total size of the comments in bytes will regularly approach 1MB or more since many of these comments are machine generated outputs of log files, command results, etc. This means that any time a JIRA issue is updated, webhooks will make a post larger than 1 MB. This will be bad from a performance perspective when the volume of updates is very high.

Is there any way to configure the webhook such that it doesn't send the entire comment history on an issue_updated event?

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events