Signed History (Issue Panel)
The issue panel shows the complete, cryptographically-verified audit history for the current Jira ticket — visible to any user with permission to view the issue.
What you see
The panel renders as an activity feed — one row per signed event, newest first. Each row is a single plain-language line:
- Author — the Jira user (or automation / AI agent) that performed the action, shown with their avatar
- Action — a human-readable description of what happened (e.g. "changed the assignee → Jane Doe", "added a comment", "transitioned to In Progress")
- Time —
DD/MM HH:mm, in your local timezone - Category lozenge — the kind of event (e.g.
COMMENT,ASSIGNEE,STATUS) - Status lozenge — the RFC 3161 timestamp authority that anchored the entry (
DIGICERT/FREETSA), which doubles as the per-entry verification indicator
Above the feed, a header shows the issue key, the count of loaded entries, and a Refresh control. A workspace-scope line shows the total verified count across the whole workspace, e.g. "Workspace chain: 247 of 247 entries cryptographically verified · SHA-256 hash chain".
Older entries load on demand — the feed shows the most recent events and reveals more with a Show more control rather than loading the entire history at once.
Trust footprint (inline)
Clicking a row's disclosure arrow expands it inline, directly beneath the row (no pop-out), showing the cryptographic details for that specific entry:
- Audit entry — the unique identifier of the chain entry
- Event — the event type this entry was created from (e.g.
avi:jira:updated:issue) - Signed at — the time the entry was recorded and signed
- Signature —
ECDSA P-256 + SHA-256 hash chain - Timestamp — the RFC 3161 timestamp authority and its qualification status (e.g.
DigiCert (NON_QUALIFIED)) - Source event ID — the original Jira event ID this entry was created from (useful for tracing back to the Jira event log)
- Verify offline — a note explaining that to check the entry independently you export the workspace evidence bundle from the admin page and open
verify.htmlinside the ZIP in any browser, plus a How offline verification works link to the documentation
Verification status
| Status | Meaning |
|---|---|
| ✅ Verified | Signature valid, hash chain intact, timestamp token present |
| ⚠️ Pending | RFC 3161 timestamp token has not yet been resolved (temporary state during high load) |
| ❌ Failed | Signature invalid or hash chain broken — this is a tamper signal |
A workspace-scope subtitle below the table shows the total count of verified entries across the entire Jira workspace, e.g. "247 of 247 workspace entries cryptographically verified · SHA-256 hash chain".
Events captured
The following Jira events produce a signed chain entry:
- Issue created
- Issue status transitioned
- Issue field edited (priority, assignee, labels, due date, etc.)
- Comment added, edited, or deleted
- Attachment added or removed
- Issue link created or removed
- Watcher added or removed
- Version released (for project-level events)
Each event type is deduplicated — if Jira fires multiple overlapping events for a single user action (e.g., an issue update that triggers both a field change and a status change), only one chain entry is created per distinct user action.
Free tier
On the free tier, the panel footer shows an upgrade call-to-action alongside the How offline verification works link. The chain and all cryptographic features are fully intact on the free tier — only retention (30 days) and export count (10/month) are limited.