GTM Playbooks for Jira

Overview

GTM Playbooks for Jira lets your team apply pre-built checklist templates — “playbooks” — to Jira issues in one click, instead of rebuilding the same checklist from scratch every time.

The app adds two places to your Jira site:

• GTM Playbook Library — reached from Jira’s Apps menu. Browse playbooks by category; create, edit, duplicate, and delete them.
• GTM Playbooks panel — on any Jira issue. Apply a playbook, tick items off, see progress, replace or remove.

It ships with 16 built-in playbooks across Marketing, Sales, and Agency — each a complete 10-step checklist. Every one of them is editable.

The app runs entirely on Atlassian Forge inside your own Atlassian cloud site. It makes no calls to Jira’s REST API, sends no data to any external service, and has no account to create.

Getting Started

1. Install the app from the Atlassian Marketplace onto your Jira Cloud site.
2. That’s it. The 16 built-in playbooks are seeded automatically the first time someone opens the library. There is no configuration screen, no API key, and no account to create.
3. Open Apps → GTM Playbook Library to see what you got.

If the library looks empty on the very first load, give it a moment and click Try again — seeding happens on that first read.

The Playbook Library

Open it from Jira’s Apps menu → GTM Playbook Library.

Each row in the list shows the playbook name, a category badge (Marketing, Sales, or Agency), the item count — e.g. “10 checklist items” — and three actions: Edit, Duplicate, and Delete.

The dropdown at the top filters the list. It has four options: All categories, Marketing, Sales, and Agency. If a filter matches nothing you’ll see “No playbooks in this category” — switch the filter or create a new playbook.

Duplicate takes one click and opens no dialog. It creates a copy named {original name} (Copy) with the same category and items. This is the fastest way to build a variant: duplicate, then edit the copy.

Delete asks you to confirm first, and tells you exactly what will happen: the playbook and its items are deleted for everyone on the site, permanently, and checklists already applied to issues are not affected.

There is no admin-only mode. Any user who can open the library can edit or delete any playbook in it, including the built-in ones. Access is controlled entirely through your Jira site’s own permissions.

Applying a Playbook to an Issue

1. Open any Jira issue and find the GTM Playbooks panel.
2. If the issue has no checklist yet, you’ll see “No playbook applied yet.”
3. Use the Choose a playbook dropdown. Options are labelled Playbook Name (Category) — for example Website Launch (Marketing).
4. Click Apply playbook.

The checklist appears on the issue with a checkbox per item and a progress bar reading something like 7/10 completed. Tick items off as the work happens — changes save immediately, and everyone watching the issue sees the updated progress.

Replacing or Removing a Checklist

An issue holds one checklist at a time.

Once a checklist is applied, the picker below it stays available and its button now reads Replace checklist. Because replacing overwrites the current checklist, the app asks you to confirm and tells you how much progress you’re about to lose. Choose Cancel to keep what you have, or Replace checklist to go ahead.

Progress is not recoverable after a replace.

Remove checklist clears the checklist from the issue entirely, returning the panel to its empty state. The playbook itself is untouched and stays in the library.

Creating and Editing Playbooks

Click New template at the top of the GTM Playbook Library, or Edit on an existing row. The form has three fields:

• Template name — required, up to 120 characters. e.g. Website Launch
• Category — required. One of Marketing, Sales, or Agency.
• Checklist items (one per line) — required. One item per line; blank lines are dropped and surrounding whitespace is trimmed.

Paste your steps straight in, one per line, then click Create template (or Save changes when editing). If something is missing, the form tells you: “Choose a category before saving.” or “Add at least one checklist item.”

Editing an existing playbook changes it for everyone on the site from that point forward. It does not change any checklist already applied to an issue.

The 16 Built-in Playbooks

Every built-in playbook has 10 items. All of them can be edited, duplicated, renamed, or deleted.

Marketing: Marketing Campaign Launch · Website Launch · Product Launch · SEO Audit · Content/Blog Launch · Email Newsletter Launch

Sales: Sales Handoff · Sales Demo Prep · Deal Closing Checklist · Sales Discovery Call Prep

Agency & Client Work: Client Onboarding · Client Offboarding · QBR Prep · Creative Project Kickoff · Client Renewal/Upsell Prep · Customer Onboarding

As an example, Website Launch contains: Finalize sitemap and page content · Complete cross-browser and mobile QA · Verify SEO metadata and redirects · Set up analytics and conversion tracking · Test all forms and CTAs · Confirm SSL certificate and domain DNS · Run page speed and accessibility checks · Set up 404 and error page monitoring · Notify stakeholders of the go-live date · Monitor traffic and errors post-launch.

And Client Onboarding contains: Send welcome email and kickoff agenda · Collect brand assets and access credentials · Confirm project scope, timeline, and deliverables · Schedule a recurring check-in cadence · Set up the project in tracking/reporting tools · Introduce the assigned account team · Review reporting format and KPIs with the client · Confirm invoicing and billing contacts · Document the client’s preferences and communication style · Send an onboarding summary and next steps.

How Your Data Is Stored

Everything lives in Atlassian’s Forge storage, inside your own Atlassian cloud site. The app stores two kinds of record: your playbook library — one record per site holding every playbook’s name, category, and items — and an applied checklist per issue, holding a copy of the item text, which items are ticked, the playbook’s name, and when it was applied.

Applied checklists are snapshots. This is the most important thing to understand about the app. When you apply a playbook, the issue gets its own copy of the steps. From that moment the checklist on the issue is independent of the playbook it came from:

• Editing a playbook’s items changes the library, not checklists already on issues.
• Renaming a playbook does not rename checklists already applied.
• Deleting a playbook does not break checklists already applied — they keep working.
• Applying the playbook to a new issue uses whatever the current version says.

What your team ticked off in March still reads exactly as it did in March.

If a future release of the app adds a new built-in playbook, it appears on your site automatically. A built-in you deliberately deleted is not brought back.

The app makes no Jira REST API calls at all. It never reads your issue summaries, descriptions, statuses, assignees, comments, custom fields, or user profiles. The only Jira data it uses is the issue ID of the issue whose panel is open, which it uses as a storage key. It requests exactly one permission scope, storage:app, and declares no external network permissions — so the Forge platform blocks any outbound request, including to Makeinfo. Full detail is in the privacy policy.

Limits

• Template name — up to 120 characters
• Checklist items per template — up to 100
• Length of each checklist item — up to 500 characters
• Total playbook library size — growth is refused past roughly 200 KB
• Categories — fixed: Marketing, Sales, Agency. Custom categories are not supported.
• Playbooks applied per issue — one at a time; applying a new one replaces the current one

For scale: the 16 built-in playbooks together take up about 8 KB, so the library limit is generous. If you ever hit it, delete or shorten some templates — deletes always work, even when the library is already over the cap.

Licensing and Billing

GTM Playbooks for Jira is a paid app sold through the Atlassian Marketplace. There is one edition — no free plan and no feature-limited tier.

Atlassian handles everything about money: pricing, the evaluation period, small-site pricing rules, taxes, invoices, and refunds. Makeinfo does not process your payment. An evaluation behaves exactly like a paid install — every feature is available during the trial.

If your subscription lapses, both the library and the issue panel stop showing their normal interface and display a renewal message instead. Nothing is deleted. Your playbook library and every checklist already applied to an issue stay in storage exactly as they were, and access returns as soon as the subscription is active again.

Uninstalling is different. Uninstalling the app removes its Forge storage through Atlassian’s standard uninstall path. That removal is permanent, and Makeinfo holds no copy to restore from — export anything you want to keep before uninstalling.

Troubleshooting

“Couldn’t load the playbook library” / “Couldn’t load playbooks” — a transient read failure. Click Try again. If it persists, reload the page.

“Someone else changed the playbook library while this page was open.” — another person on your site edited the library while your page had an older copy of it. The page has already refreshed itself; click Save again and it will go through. Your typed content is preserved in the form.

“The playbook library is full.” — you’ve reached the storage limit for the library as a whole. Delete playbooks you don’t use, or shorten long ones. Deleting always works even when you’re over the limit.

“Your GTM Playbooks subscription is inactive” / “Subscription inactive” — the site has no active subscription. Renew through the Atlassian Marketplace and access returns immediately; nothing has been deleted.

“This panel could not identify the current issue.” — the panel could not read which issue it’s on. Reload the issue page.

Two people ticking items on the same issue at once — changes save as you click, and the last write wins. If two people tick different items at the exact same moment, one may need to be re-ticked. Reload the panel to see the current state.

FAQ

Does editing a playbook change checklists already on issues? No. Applying a playbook copies its steps onto the issue. Editing, renaming, or deleting the playbook afterwards never rewrites a checklist that’s already applied.

Who can edit the built-in playbooks? Anyone who can open the GTM Playbook Library. The app has no admin-only mode and no locked templates, by design. Restrict access through Jira’s own permissions if you need to.

Can I add my own categories? No. The three categories — Marketing, Sales, and Agency — are fixed.

Can I apply two playbooks to the same issue? No. An issue holds one checklist at a time; applying a second playbook replaces the first, with a confirmation prompt.

Can I assign checklist items to people, or give them due dates? No. Items are plain text with a checkbox. Assignees, due dates, and cross-issue reporting are not features of the app.

Does it work with Confluence? No. The app is Jira Cloud only.

Does it work on Jira Data Center or Server? No. It’s a Forge app and runs on Jira Cloud only.

What happens to my data if I uninstall? Atlassian removes the app’s storage as part of the uninstall. That’s permanent — export anything you want to keep first.

Does any of my data reach Makeinfo? No. The app declares no external network permissions, so Forge blocks any outbound request it could make. We have no server involved and no way to see your data.

Support

Email [email protected] or use the contact page. See also the product page, the privacy policy, and the terms of service.