Sources
Jira
Capture decisions from Jira issues with bi-directional linking.
UpdatedMay 13, 2026
On this page
Jira connects delivery work to decision records.
What Jira does
- Connects a Jira Cloud site to Verachi.
- Listens for configured issue rules.
- Creates decisions from labeled Jira issues.
- Routes decisions by Jira project key.
- Writes a remote link back to the Jira issue.
Connect Jira
- Open Integrations.
- Open Jira.
- Click Connect.
- Authorize Verachi with Atlassian.
- Confirm the Jira webhook is registered.
Create a rule
- Open Integrations > Jira.
- Click New rule.
- Choose the Jira behavior.
- Enter the source project key, such as
VER. - Choose the Verachi project.
- Save.
Capture a decision
- Add the configured decision label to a Jira issue.
- Verachi reads the issue summary, description, labels, status, and project.
- Verachi creates a decision from a Verachi-written conclusion and links it to the target project.
- Jira receives a remote link back to the Verachi decision.
What Verachi reads and stores
Reads
- Issue key, summary, description, labels, status, and project metadata
Stores
- Decision record
- Jira issue permalink
- Verachi-written conclusion and optional rationale
- Source metadata such as issue ID, issue key, project key, labels, status, and update time
Verachi does not store the raw issue description, comments, or changelog text for integration capture.
Writes back
- Remote link from the Jira issue to the Verachi decision
Troubleshooting
- The Jira site must be connected.
- The webhook must point to the current Verachi instance.
- The issue must receive the configured label after the rule exists.
- The Jira project key must match the rule source.