Skip to main content
The Jira integration captures issue lifecycle activity: created and updated issues, assignments, comments, status transitions, sprint movement, and project changes. Combined with GitHub and AI coding session data, this gives Cogniscape a complete picture of what your team is working on, who is involved, and how work moves from backlog to delivery. This setup needs to be done once per Jira site (or for each Jira instance you want Cogniscape to observe). Only a Jira administrator can create and manage webhooks.
Both the Webhook URL and the signing secret are exclusive to your account. Keep the secret private — the endpoint rejects every request that does not include the matching secret.

​
Choose exactly one setup path

Jira Cloud and Jira Data Center / Server use different authentication mechanisms. Follow the section that matches your deployment — do not configure both for the same Jira instance.

​
Jira Cloud

Use this path only when your Jira is hosted by Atlassian Cloud.
1

Open Jira webhook settings

In Jira Cloud, go to Settings → System → Webhooks, then create a new webhook.
2

Give it a label

Use something descriptive like Cogniscape so you can identify it later.
3

Paste the Webhook URL

Use the following URL, replacing <your-customer-key> with the key from the Customer Portal:
4

Add the signing secret

Paste the secret from the Customer Portal (Get Started → Jira Integration) into Jira’s Secret field. Cogniscape uses it to verify that incoming events are genuinely from your Jira site.
Do not click Generate secret. That button makes Jira create its own value, but Cogniscape and Jira must use the same secret already registered for your account. Jira may warn that the secret cannot be displayed again after saving — that’s fine, paste the Cogniscape secret and save.
5

Choose which events to send

Select the development activity events Cogniscape uses to build the Jira layer of your graph:
  • Issue: created, updated, deleted
  • Comment: created, updated, deleted
  • Worklog: created, updated, deleted
  • Issue link: created, deleted
  • Sprint: created, updated, deleted, started, closed
  • Project: created, updated, deleted
  • Version: created, released (moved, merged, updated, and unreleased are optional)
Leave Board, Issue Type, User, Filter, Attachment, Entity property, and Feature status change unchecked. Those are configuration or admin events, not development activity.
6

Review delivery options and save

Leave Exclude body unchecked — Cogniscape needs the JSON event body.JQL is optional. Leave it blank to receive all projects, or add a filter to restrict issue events. Sprint, Version, and Board events are sent for all projects and do not follow the JQL filter.

​
Jira Data Center / Server

Use this path only when your organization hosts Jira Data Center or Jira Server.
1

Open admin webhooks

In Jira administration, go to System → WebHooks → Create.
2

Paste the Webhook URL

Use the same URL as above, with your customer key from the Customer Portal:
3

Add the custom HTTP header

Add this header so Cogniscape can authenticate requests from your Jira instance, using the secret from the Customer Portal:
4

Select the same development events

Use the same event selection from the Jira Cloud section: Issue, Comment, Worklog, Issue link, Sprint, Project, and Version. Leave configuration and admin events unchecked.
5

Leave body enabled, save, and check egress

Leave Exclude body unchecked, then save. Make sure your Jira server can make outbound HTTPS requests to https://api.cogniscape.app through your egress firewall.
Create the webhook from the admin WebHooks screen above — that webhook type does not expire. Avoid REST or dynamic webhooks, which expire after 30 days.

​
Verify the webhook

After saving, trigger a test by creating or updating an issue in Jira. Check the webhook delivery log to confirm events are being sent with a 200 response.

​
Supported resources

Cogniscape processes these Jira webhook resource types:
Resources not listed above are received but silently ignored. Selecting only the events above keeps your knowledge graph free of configuration and admin noise.

​
Why the secret matters

Cogniscape verifies every incoming Jira event against the secret saved in the Customer Portal before processing it. Without a matching secret, webhook events are rejected.
Treat the secret as sensitive. If it’s exposed, regenerate it in the Customer Portal and update the Jira webhook (Cloud secret field or Data Center header) before relying on new events. Old secrets stop working immediately after rotation.