Datum

Docs → Signet

Documentation · Jirav2.8.1

Signet docs

Signet adds an approval step to Jira issues. You request sign-off, and approvers approve or reject in the Signet — Approvals panel on the issue view. An optional workflow validator can block a transition until the request is approved.

Getting started

Before you install

  • Jira Cloud. Signet is a Forge app (Runs on Atlassian). There is no Data Center version.
  • A Jira admin installs the app. Adding the workflow validator also needs a Jira admin.
  • To request approval you need permission to edit the issue. The project settings page is for project admins.
  • Standard-plan features need a Standard licence. The paid plan is still in Atlassian review, so these features stay locked until it is on sale.

Install and first use

  1. Open the panel on an issueOpen any issue and find the Signet — Approvals panel. It shows the request status, who approved, who rejected and who it's still waiting on.
  2. Request approvalPick an Approval type: Any approver, All approvers or Quorum (set Approvals required). Add people under Approvers, or a Jira group or project role under Groups and project roles, then click Request approval.
  3. Approvers are notifiedSignet posts a Jira comment that @mentions each approver, so Jira notifies them as usual. The comment links to the issue and points to the Signet — Approvals panel.
  4. Approve or rejectApprovers click Approve or Reject in the panel, with an optional Reason. When the request is approved or rejected, Signet posts a comment that mentions the requester.
  5. Find your queue with JQLRun signetStatus = "pending" AND signetPendingApprover = currentUser() in Jira search to list everything waiting on you. Save it as a filter to reuse it.
  6. Add the Approvals gadgetOn a Jira dashboard, click Add gadget and pick Signet — Approvals. It lists Waiting on me (requests you still have to decide) and My requests (your own requests that are still pending), up to 20 each, with a link to each issue. In its Edit settings you can narrow it to one Project and tick Also show how many approvals are pending. Free.
  7. Ask RovoIf your site has Rovo, open the Signet Approvals agent or ask Rovo chat What approvals are waiting on me? It lists the requests you still have to decide. Ask it to approve or reject one by issue key, with an optional comment, and Rovo asks you to confirm first. The decision goes through the same checks as the panel: only a pending approver (or their delegate) can decide, and stages and the self-approval guard still apply. Free.
  8. Optional: block a transitionA Jira admin opens the workflow, selects a transition (for example to Done), adds a validator and chooses Signet approval required. Issues with a pending or rejected request can't use that transition. Issues with no request move freely.

Configuration

Approval types

  • Any approver: one approval is enough.
  • All approvers: everyone named must approve.
  • Quorum: a set number of approvals is required.
  • In order (approval chain) and Stages are Standard-plan options. Chains and stages take named people, not groups or roles.

Groups and project roles

You can name a Jira group or a project role instead of people. Signet looks up the members when the request is made, and each member counts as one approver. Membership is fixed for that request; later group changes don't affect it.

Who can request or replace a request

  • Anyone who can edit the issue can request approval.
  • Replacing a request that is in progress or already has decisions is limited to a project admin, or to the requester before anyone has decided.
  • A new request can be made on an issue whose request was rejected (Request approval again).
  • If a project admin's rule applies to the issue, only a project admin can change its approvers.

Self-approval guard (free)

In Project settings → Signet — Approval rules, the Separation of duties toggle Block requesters from approving their own requests is on by default. The requester can't approve their own request, even as someone's delegate or out-of-office substitute, and is left out when a group or role is expanded. They can still reject. For requests created by a rule, the issue's reporter counts as the requester.

Jira Service Management

Signet works on service requests too. Agents open the Signet panel on the request in the agent view and request approval the same way.

  • Signet's request, outcome and reminder comments are internal notes, so customers never see them on the portal or by email.
  • Customers see an Approval panel on their request in the portal: waiting for approval (with progress, such as 1 of 2), approved or not approved. It doesn't show approver names or reasons. This is free.
  • Customer approvers (Standard): on an any, all or quorum request, the agent can also pick customers from the request's participants. They see Approve and Reject, with an optional reason, in the portal's Approval panel, once, while the request is pending. The reason is shown to agents only. To make someone a customer approver, add them as a request participant first.
  • With the self-approval guard on, the person who raised the request (the reporter) can't be an approver on it, in addition to the agent who asked for approval.
  • Routing rules (Standard) can use the Request Type field: enter the request type's name, such as Request new hardware, or its id.

Standard-plan settings (project admins)

These are on the Signet — Approval rules project settings page and need a Standard licence. The paid plan is in Atlassian review, so they are not yet available to buy.

  • Required approvers by issue type: issues of a chosen type get a request as soon as they are created, and approvers are notified.
  • Routing rules (first match wins): pick approvers from field values such as priority or a custom number field. If the field changes before anyone decides, the request moves to the newly matching approvers.
  • Overdue-approval reminders: a daily reminder comment that @mentions approvers who haven't decided after the set number of days.
  • Escalation: @mention chosen people once when a request is still pending after a set number of days.
  • Approval history: Load history for the project and Export CSV.
  • Delegate (in the issue panel): Name a delegate who can approve or reject on your behalf until you remove them, or Set an out-of-office substitute for a date range. The record, the issue comment and the history (Decided by column and CSV) show who actually decided and on whose behalf. A delegate can't approve their own request, and can't be used to approve yours while the self-approval guard is on. Removing the delegate ends their rights immediately.

Charts and insights

Approval insights on the Signet — Approval rules project settings page, for the last 30 or 90 days. Free: requested, approved, rejected, pending and overdue counts. Standard: median and P85 time to decision, each approver's time to decide, a weekly requests vs decisions chart and the 10 oldest pending requests.

Language

Available in English, German, French and Spanish. The app follows each person's Jira language setting; Rovo answers, exports and comments the app posts stay in English.

Free vs Standard

Plans and prices below are read from the same pricing file the app uses. Atlassian bills per user per month on your site's user tier, and the price per user steps down at larger tiers. See all pricing.

Free

Free

  • Single- and multi-approver sign-off on the issue (all / quorum / any)
  • Approve or reject with a reason
  • Approvers notified by Jira @mention when a request is made
  • Find pending approvals with JQL (signetPendingApprover = currentUser())
  • Optional workflow validator: block a transition until approved
  • Auditable decision record — who approved what, and when
  • Anyone who can edit the issue can request approval — no admin rights

Standard

$0.75 / user / month

Free for sites up to 10 users. 30-day free trial.

  • Approval chains — approvers sign off in order, one after another
  • Routing by field values — e.g. priority or amount picks the approvers (first match wins)
  • Multi-stage approvals — up to 10 stages, each any / all / quorum
  • Out-of-office substitutes who can approve on your behalf
  • Escalation — alert chosen people when an approval is overdue
  • Required approvers per issue type — set default sign-off rules project-wide
  • Jira Service Management: named customers approve or reject on the customer portal
  • Approval history across all issues + CSV export
  • Automatic reminders on overdue approvals (a Jira comment to pending approvers)

Limits

  • Up to 5 groups or project roles per request.
  • Up to 50 approvers per request once groups and roles are expanded.
  • Multi-stage approvals: up to 10 stages (Standard).
  • Routing rules: up to 50 per project, each with 1 to 10 conditions (Standard).
  • Escalation: up to 5 people; the default is 7 days (Standard).
  • Reminders are off by default; the default threshold is 3 days (Standard).
  • One delegate or out-of-office substitute per person at a time. A substitute can be set at most 365 days ahead; a delegate has no end date (Standard).
  • Delegation isn't passed on: a delegate's own delegate can't act for you.
  • No plan limit on approvers per issue beyond the 50-person cap above.
  • The Rovo action lists up to 20 approvals waiting on you, like the gadget.
  • The Approvals gadget shows up to 20 issues per list, with a link to the full search. My requests covers requests made after the gadget arrived (v2.5); older requests appear there once someone decides on them.

Data & privacy

What Signet stores

  • Approval records are kept in Forge hosted storage for your site: the approvers and approval type, who requested and when, and each decision (who decided, approve or reject, the optional reason, the time, and the delegate or substitute if one decided on someone's behalf).
  • Project settings are kept in Forge storage too: the self-approval setting, issue-type rules, routing rules, reminder and escalation settings, and each person's delegate or out-of-office substitute.
  • Each issue gets a signet-approval issue property (status, approvers, pending approvers, requester, request time) so JQL can search it. The validator reads Forge storage, not this property, so editing the property doesn't get around it.
  • Notifications are ordinary Jira comments, stored by Jira.
  • Signet stores Atlassian account IDs only. It reports them to Atlassian's personal-data API weekly and replaces closed accounts with "Removed user".
  • No external servers: the manifest declares no outbound network access, so nothing is sent outside Atlassian.

Signet runs on Atlassian Forge. Data it stores sits in Forge hosted storage for your site, which Atlassian pins to your product's region. See Trust & security, the Privacy Policy and the DPA.

Permissions (scopes)

ScopeWhy Signet needs it
read:jira-workRead issues, fields, project roles and your permissions on the issue.
write:jira-workPost the request, outcome and reminder comments (internal notes in service projects) and write the searchable issue property.
storage:appKeep approval records and project settings in Forge hosted storage.
report:personal-dataReport stored account IDs to Atlassian weekly and erase closed accounts.
read:group:jiraRead a group's members when a request names a group, and list groups in the request form.
read:user:jiraPart of the narrowest scope set Jira accepts for reading group members and listing groups.
read:avatar:jiraPart of the narrowest scope set Jira accepts for reading group members and listing groups.

FAQ & troubleshooting

A transition is blocked with a Signet message. What do I do?

The Signet approval required validator is on that transition and the request isn't approved yet. The message says how many approvals are in so far. If the request was rejected, make a new one with Request approval again in the panel. If the message says Signet "couldn't check this issue's approval just now", try the transition again: the validator blocks when it can't read the record.

Will the validator block issues that never needed approval?

No. Issues with no Signet request, and no project rule that applies, pass the validator. You can add it to a shared transition safely.

Why can't an approver see the Approve button?

Only named approvers (or their delegate or active out-of-office substitute) can decide. In an approval chain or stages, it must be their turn. If they requested the approval themselves and the self-approval guard is on, they can only reject.

Why can't I request approval on an issue?

You need permission to edit the issue. If a request is already in progress, only a project admin, or the requester before anyone has decided, can replace it. If a project admin's rule covers the issue type, only a project admin can change its approvers.

How do approvers find what's waiting on them?

Use the JQL signetStatus = "pending" AND signetPendingApprover = currentUser(). Other searchable fields are signetApprover, signetRequester and signetRequestedAt. Or add the Signet — Approvals dashboard gadget.

Can approvers approve from email or Slack?

No. Signet sends nothing outside Atlassian. The mention email from Jira links straight to the issue, where approvers decide in the panel.

Does it work in Jira Service Management?

Yes. Agents request and decide in the Signet panel on the request in the agent view, Signet's comments are internal notes, and customers see the approval status (not who approved) in an Approval panel on their portal request. On Standard, customers an agent names from the request's participants can approve or reject right there in the portal.

Can I buy the Standard plan now?

Not yet. The paid tier is in Atlassian review. Until it is approved, Standard features show as locked and everything in the free plan keeps working.

Changelog

Every release and what changed: Signet changelog.

Getting help

Email support@datadir.co with your site URL and what you saw. Our target is a first response within 1 business day. See Support for what to include, and Status for known issues.