Details on demand
Timestamp and scope
Open the compact detail to see when and what was signed.
Content-aware issue sign-off
Know exactly which issue content was approved.
Signlight adds a simple traffic-light sign-off to Jira issues. Green means the relevant content is signed. Yellow means it changed. Red means there is no active sign-off.
See it in Jira Built on Atlassian Forge
SignedSummary, description and attachments approved
MP-1 relevant content updated
Issue changedReview the updated content
MP-1UnsignedSignedChanged
Native to the issue
No dashboard. No second workflow.
Sign and check the status in Jira's issue context, where the work and its supporting detail already live.
The traffic-light workflow
Only meaningful content changes the light.
Signlight fingerprints the summary, description and attachment set. Routine comments and status changes do not invalidate an otherwise current sign-off.
Green
Issue content signed
The active sign-off matches the issue's relevant content.
Red
Unsigned or revoked
No active sign-off exists for the issue.
Small by design
Visible accountability without approval theatre.
Signlight is for lightweight internal acknowledgement and approval. It is not a regulated or legally binding e-signature product.
Atlassian identity
People sign with the account already logged into Jira.
Content aware
Summary, description and attachments define the signed state.
Revocable
Only the active signer can revoke, with a bounded audit event.
No content copy
Signlight stores a fingerprint and identifiers—not issue content.
Hosted on Forge
Your sign-off flow stays inside Atlassian.
The app runs on Atlassian Forge, uses Forge app storage and declares no external network egress. There is no separate Signlight account, password or external dashboard.
Marketplace launch
Make issue approval visible.
Signlight for Jira is entering Atlassian Marketplace review.