Documentation

AcceptDeck for Jira Documentation

Last updated: September 6, 2026

AcceptDeck packages Jira deliverables into a focused review and records an approval or request for changes against the related Jira issue.

Requirements

• A supported Jira Cloud site.
• An active AcceptDeck Marketplace license or evaluation.
• Jira permissions appropriate to the action being performed.
• Jira Service Management when using its customer portal panel.

Create and publish a package

1. Open the relevant Jira issue and locate the AcceptDeck panel.
2. Add the package title, summary, due date, deliverables, acceptance criteria, and only those Jira attachments intended for the reviewer.
3. Review the draft carefully. Internal Jira fields and attachments are not automatically safe to disclose merely because they exist in Jira.
4. Publish the package. Publishing creates a revision so later decisions refer to a defined version.

Jira Service Management review

An authenticated JSM customer who can access the related request can open the AcceptDeck review panel. The App verifies that user’s request access before returning package information. The customer may approve a deliverable or request changes and add a comment.

External review link

1. A licensed Jira user with edit permission creates an external page and chooses an expiry period.
2. Set the required review password and share it through a different channel from the link.
3. Send the link only to the intended reviewer. The URL contains no bearer access token, but anyone who obtains both the link and password may be able to view its deliberately published content.
4. Revoke the link immediately when it is no longer required or if it may have been disclosed.

External links may be active for no more than 90 days. Expiry and revocation invalidate access. Do not put special-category, secret, regulated, or unrelated personal data in an acceptance package.

Decisions and Jira comments

A reviewer chooses Approve or Request changes and may submit a comment. AcceptDeck records the decision, actor label or identifier, timestamp, and package revision. It also attempts to add a corresponding Jira comment. If Jira rejects that comment, the App may preserve the decision but report that the Jira comment could not be posted.

Attachments

Only select attachments that the reviewer is permitted to receive. Before preparing a download, AcceptDeck verifies that the attachment is included in the package and still belongs to the related Jira issue. Removing or changing an attachment in Jira can make it unavailable from the package.

Deletion and privacy requests

Authorized Jira users can remove drafts or published package information through supported App actions. Uninstalling may not immediately remove every Jira issue property or Forge record. Jira administrators may request assistance at privacy@acceptdeck.com.

Troubleshooting

• License required: confirm the Marketplace trial or subscription is active.
• Access denied: confirm the user can view the Jira issue or JSM request and has edit permission for management actions.
• External page unavailable: the link may be incorrect, expired, revoked, password-protected, or rate-limited.
• Attachment unavailable: confirm it remains attached to the Jira issue and published in the current package.

For help, see the Support Policy or email support@acceptdeck.com.