Autopack
HomeContents

User guide

How to use Autopack in Jira Cloud

This guide walks through the end-to-end workflow: install → configure → close an incident → review the draft → approve → action items get created and linked back to the incident.

Audience

  • Jira admins (install/config)
  • Incident owners (review/approve)
  • SRE / platform teams (postmortem follow-through)

Contents

  1. Prerequisites
  2. Getting started (quick checklist)
  3. Install (Jira Cloud)
  4. Permissions & access
  5. Configuration reference
  6. The workflow (high level)
  7. Step-by-step with screenshots
  8. Troubleshooting

Prerequisites

  • Jira Cloud site admin access (to install + configure apps).
  • A Jira project where incidents live (e.g., an incident issue type in JSM, or a dedicated “Incidents” project).
  • Agreement on what “closed” means for your team (status category “Done” or explicit status names).
  • Permission to create action-item issues in a target project (usually the same project as the incident, but it can be separate).

Getting started (quick checklist)

Jira admin

  1. Install Autopack on your Jira site.
  2. Configure: incident project(s) + issue type(s).
  3. Configure: what counts as “closed” (Done category or status names).
  4. Configure: where action items should be created + link type.

Incident owner / reviewer

  1. Close the incident in Jira.
  2. Review the generated draft comment.
  3. Ensure the Action items section contains bullet points.
  4. Approve in the Issue Panel (View app actions → Autopack → Approve draft).
  5. Fallback: comment autopack approve at the start of a comment.
  6. Confirm action items were created + linked, and assign owners if needed.

Beta install note

During private beta we may install Autopack via a development/preview flow rather than the Marketplace. The workflow inside Jira is the same.

Install (Jira Cloud)

Where to find “Manage apps”

In Jira Cloud, the most reliable entry point is the Universal Plugin Manager (UPM):

https://YOUR-SITE.atlassian.net/plugins/servlet/upm

Replace YOUR-SITE with your Jira site subdomain. From there you can search for Autopack, install/enable it, and manage versions.

Permissions & access

  • Autopack needs access to read incident details, changelog, and comments to generate the draft.
  • To create action items, Autopack needs permission to create issues in the configured action-item project.
  • If action items are created in a different project than the incident, confirm permissions in that target project (issue create + link).

Configuration reference (v0.1)

  • Scope: project keys + incident issue types
  • Close detection: status category “Done” (recommended) or explicit status names
  • Enable label (optional): only run when label is present (e.g. autopack)
  • Action items: target project + issue type + link type + max items
  • Ownership defaults: assignee strategy (inherit) + due date offset (e.g. +7d)

Workflow (high level)

1Install + configure

Pick your incident projects/types and where follow-up tasks should land.

2Close incident

Move the incident to your configured closed status.

3Autopack generates draft

Draft + evidence timeline are posted and stored for safe processing.

4Human reviews

Make any edits and ensure the Action items section is correct.

5Human approves

Approve in the issue panel (Approve draft). Fallback: comment ‘autopack approve’.

6Autopack creates action items

Autopack creates Jira issues, links them back, and posts a receipt.

Step-by-step (with screenshots)

Install Autopack from ‘Apps’

Jira Admin installs Autopack on your Jira Cloud site (development/beta install flow differs from Marketplace).

Screenshot /user-guide/01-install.png
Jira Apps page showing Autopack installed (placeholder)
/user-guide/01-install.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Configure Autopack settings

Choose which projects + issue types are considered incidents, and where action items should be created.

Screenshot /user-guide/02-config.png
Autopack settings screen (placeholder)
/user-guide/02-config.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

(Optional) Add enable label to an incident

If you use an enable label (e.g., ‘autopack’), add it to the incident so Autopack runs only when desired.

Screenshot /user-guide/03-label.png
Jira issue labels including autopack (placeholder)
/user-guide/03-label.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Close the incident (transition to Done/Closed)

When the incident is moved to a ‘Done’ status category (or your configured closed statuses), Autopack generates a draft.

Screenshot /user-guide/04-close.png
Jira workflow transition to Done (placeholder)
/user-guide/04-close.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Draft is posted + stored

Autopack posts a draft comment and stores the full Markdown draft in an issue property for reliable follow-up actions.

Screenshot /user-guide/05-draft-comment.png
Jira comment containing Autopack postmortem draft header (placeholder)
/user-guide/05-draft-comment.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Review and update the Action items section

Ensure the draft’s ‘Action items’ section contains bullet points (e.g., ‘- Do X’). Autopack creates one follow-up issue per bullet.

Screenshot /user-guide/06-review.png
Reviewing the draft and action items section in Jira
/user-guide/06-review.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Approve in the Issue Panel

Open ‘View app actions’ → ‘Autopack’ and click ‘Approve draft’. (Fallback: add a comment that starts with ‘autopack approve’.)

Screenshot /user-guide/07-approve.png
Autopack Jira issue panel showing the Approve draft button
/user-guide/07-approve.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Action items are created and linked

Autopack creates Jira Task issues for each action item bullet, links them back to the incident, and posts an approval receipt.

Screenshot /user-guide/08-actions-created.png
Jira showing created linked action items (placeholder)
/user-guide/08-actions-created.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Approval receipt comment

Autopack posts a clear approval receipt (distinct from the draft header) listing created issues.

Screenshot /user-guide/09-approval-receipt.png
Jira comment titled Autopack approval receipt (placeholder)
/user-guide/09-approval-receipt.png
Tip: keep sensitive data out of screenshots (emails, internal URLs, tokens). Use demo incidents.

Troubleshooting

No draft generated after closing

  • Confirm the incident matches configured project + issue type.
  • Confirm the incident is transitioned into your configured “closed” definition (status category “Done” or explicit status names).
  • If an enable label is configured, confirm the label is present on the incident.
  • Wait 10–30 seconds and refresh — Jira events + comments can be eventually consistent.

Approval didn’t create action items

  • Ensure the Action items section contains bullet points (e.g., - Do X).
  • Approve via the Issue Panel button first. Fallback: ensure your approval comment starts with autopack approve (at the very start of the comment).
  • Jira search can lag; refresh and check the incident’s linked issues.
  • If the action-item project/type differs from the incident project/type, confirm permissions in the target project.

Duplicates

Autopack is designed to be idempotent: re-approving should not create duplicates. If you see duplicates, report the incident key and we’ll investigate.