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
Each entry in the signed history table shows:
| Column | Content |
|---|---|
| Time | DD/MM HH:mm:ss — the time the event was recorded and signed, in your local timezone |
| Author | The Jira user who performed the action |
| Activity | A human-readable description of what happened (e.g., "Transitioned to In Progress", "Added comment", "Changed priority from Medium to High") |
| Status | A lozenge showing the cryptographic verification status of this entry |
The panel displays the 20 most recent entries for the current issue by default.
Trust footprint popup
Clicking the status lozenge on any entry opens a trust footprint popup showing the cryptographic details for that specific entry:
- Entry ID — the unique identifier of the chain entry
- Signature algorithm —
ECDSA secp256k1(the signing algorithm used) - Timestamp authority — the name of the RFC 3161 timestamp authority that issued the timestamp for this entry (e.g.,
FreeTSAon the free tier) - Source event ID — the original Jira event ID this entry was created from (useful for tracing back to the Jira event log)
- A copy-pastable CLI verification command:
attestsys verify --entry-id <id>
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 offline verification CLI 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.