Indexing triggers allow immediate reindexing of your repositories from remote systems, sending near real-time data to Jira whenever your git data changes. This provides Jira with more frequently updated information. Setting up indexing triggers results in much faster indexing time where you don’t have to wait for the regular polling interval (every 5 minutes).
Most git providers also allow you to create webhooks at an account-level or org-level. For more information about this topic, see About GitLab Webhooks.
Getting Started
Set up webhooks for your configured integrations/repositories from remote systems by enabling the feature first.
-
From your Jira dashboard, go to the Apps menu.
-
Click Git Integration: Manage Git repositories.
-
On the sidebar, click Indexing triggers to open the Webhooks configuration page.
-
Enable the webhook feature by switching the Indexing triggers enabled setting to
ON.
Use the Webhook URL to set up webhooks for your remote git host.
The Secret Key is a secure random-generated alphanumeric string created at the time of Git Integration for Jira app installation. You can change this to a different value by generating another secret token according to your Git host.
Use this key in the form of:
<JIRA_BASE_URL>/git/webhook/reindex/<SECRET_KEY>GET, POST, or PUT and webhooks are enabled.
There is no support for other HTTP methods such as DELETE or HEAD.
See About indexing triggers in Jira Cloud for more detailed information on this topic.
For more information about triggers and event types, see Creating reindex triggers for a single repository.
Last updated: December 2025
