It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Webhook Performance With Custom Fields


My Use Case is:

My application must be notified if jira tast/issue(which has some custom fields) is getting close.

I created a Jira webhook for the above use case, which looks like below:

JQL: project = "My Project" AND "Custom Field1" is not EMPTY AND "Custom Field2" in (A,B) AND Status = "In Progress"
Issue: updated

I was able to understand that JQL with custom fields can take multiple seconds to query from the below link:

So my question is:

Let's say if we have ~2000 issues are getting updated every day in that project "My Project", in which ~1000 issues will be in status "In Progress".

So I want to know, what will be downside using the above JQL in the webhook?

I know we can create a new transition for specific use case but I don't want to add new steps because of some reasons.


Amit Kumar.

0 answers

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you