Changelog — Signet
Version numbers here are Datum release numbers. The version Jira or Confluence shows for the app is assigned by Atlassian and may differ.
v2.8.1 · 2026-11-16
- Clearer German, French and Spanish wording after a translation review, using Atlassian's own Jira and Confluence terms.
v2.8.0 · 2026-11-16
- Signet now speaks German, French and Spanish — it follows each person's Jira language.
v2.7.0 · 2026-11-16
- Approval insights on the Signet — Approval rules project settings page, for the last 30 or 90 days. Free: how many approvals were requested, approved and rejected, and how many are pending and overdue right now. Standard: median and 85th-percentile time to decision, each approver's median time to decide (chart and table), a weekly chart of requests vs decisions, and the 10 oldest pending requests. Built from the decisions Signet already records, so past approvals show up straight away.
v2.6.0 · 2026-11-15
- Rovo actions (free): ask Rovo "What approvals are waiting on me?" to list the requests you still have to decide (issue, summary, requester, when requested, stage), or ask it to approve or reject one by issue key with an optional comment. Rovo asks you to confirm before it decides. The decision goes through the same checks as the panel: only a pending approver or their delegate can decide, stages and the self-approval guard still apply, and the same comments and history are recorded. A Signet Approvals Rovo agent bundles both.
v2.5.0 · 2026-11-15
- New Signet — Approvals dashboard gadget (free): "Waiting on me" lists the requests you still have to decide, "My requests" lists your own requests that are still pending, and you can add a count of pending approvals for one project or everything you can see. Each row links to its issue.
- New JQL field signetRequester: find approval requests by who asked, e.g. signetRequester = currentUser(). It covers requests made from this version on, and older ones once someone decides on them.
v2.4.0 · 2026-11-14
- Customer approval on the portal (Standard): in Jira Service Management, an agent can name customers from the request's participants as approvers, and they approve or reject on the customer portal. The decision is recorded as theirs, marked as made on the portal.
v2.3.0 · 2026-11-14
- Permanent delegates (Standard): name someone who can approve or reject on your behalf until you remove them. The comment, panel, history and CSV record "approved by B on behalf of A". Removing a delegate ends their rights immediately.
- The self-approval guard covers delegates both ways: a delegate can't approve their own request, and a requester can't approve through their delegate.
v2.2.0 · 2026-11-14
- Works in Jira Service Management: agents can request and decide approvals on service requests. Signet's comments are internal notes, so customers never see them.
- The customer portal shows an approval status panel on the request (status and progress only, no names or reasons). Free.
- Routing rules can match the Request Type (Standard).
v2.1.0 · 2026-11-14
- Groups and project roles in multi-stage approvals and approval chains (Standard). In a chain, any one member of a group or role approves that step.
v2.0.0 · 2026-11-13
- Needs admin approval when you update: Signet asks to read Jira groups and their members, used only to look up who is in a group you add as an approver.
- Groups and project roles as approvers: with Any, All or Quorum, add a group or role next to named people. Members are looked up when you request approval, up to 50 people. Free.
- No approving your own request (on by default): the requester can't approve it, even as someone's substitute. They can still reject it. A project admin can turn this off. Free.
- Jira admins are now treated as project admins everywhere Signet checks for one.
v1.1.0 · 2026-11-13
- Approvers are told: Signet adds an issue comment that @mentions each approver, so Jira notifies them, with a direct link to the issue. You're mentioned when it's approved or rejected. Free.
- Find pending sign-offs with JQL, for example signetStatus = "pending" AND signetPendingApprover = currentUser(). Free.
- Optional "Signet approval required" workflow validator stops an issue moving through a transition while its approval is pending or rejected. Free.
- Anyone who can edit an issue can request approval. Free.
- Approval chains, where approvers sign off one after another (Standard).
- Multi-stage approvals with up to 10 stages (Standard).
- Out-of-office substitutes who can decide for you between two dates (Standard).
- Route approvals by field values, such as priority or an amount field (Standard).
- Escalation: alert named people once if a request waits too long (Standard).
v1.0.9 · 2026-11-11
- Maintenance release: updated Atlassian UI libraries. No visible changes.
v1.0.8 · 2026-10-25
- More reliable saving when several approvals or rules change at the same time.
v1.0.7 · 2026-10-25
- Fixed: a regression in overdue reminders introduced by the previous release.
v1.0.6 · 2026-10-25
- Daily overdue reminders only run on sites with a Standard licence.
v1.0.5 · 2026-10-25
- Security fix: Signet checks that you may decide before recording an approval, and reminder settings are kept per project.
v1.0.4 · 2026-10-24
- Approval rules are included in Atlassian's personal-data reporting and erasure.
v1.0.3 · 2026-10-24
- Approval history only shows the viewer's own project.
- Fixed: an Any or Quorum request that enough approvers rejected stayed pending forever. It is now marked rejected once approval can no longer be reached.
- Fixed: overdue reminders stopped for requests that already had a decision. One failing issue also no longer stops reminders for the rest.
- A policy can no longer list the same approver twice.
v1.0.0 · 2026-10-09
- First tagged release: per-issue approvals with Any, All or Quorum, reasons on each decision and a decision record. Free.
- Standard: required approvers per issue type, overdue reminders, and per-project history with CSV export.