Corkprint documentation

Get started

1. Install Corkprint from the Atlassian Marketplace (Jira admin). Every site gets a 30-day free trial through Atlassian. After that it is $44 a month for up to 10 users, then billed per user.
2. Open Corkprint from wherever your issues are:
   • a sprint's ••• menu on the backlog: Print sprint cards
   • the backlog's menu: Print backlog cards
   • the board's ••• menu: Print board cards
   • issue search, after selecting issues: Print cards
   • an issue's ••• menu: Print card
   • the project sidebar: Print cards
   • the Apps menu: Corkprint
3. When you open it from a sprint, backlog, board, search, issue or project, Corkprint loads those issues straight away and shows Opened from: with where they came from. Click Reload to load them again.
4. Untick any cards you don't want, pick a design under 2. Card design and a paper or label sheet under 3. Paper and labels, then click Print or Download PDF.

The preview in the middle shows your cards exactly as they will print. Opened from a sprint, backlog, board, search or issue menu, Corkprint fills the window; click Close when you are done.

Choose issues

The 1. Choose issues panel has a tab for each kind of source:

• Sprint: pick a Board (type in Search boards to narrow the list), then a Sprint. Active and future sprints come first, followed by the five most recent closed sprints. Kanban boards show This board has no sprints.
• Backlog: pick a board. Prints the board's backlog (issues not in a sprint).
• Board: pick a board. Prints all issues that belong to the board.
• JQL: type any JQL query. If your query ends with ORDER BY, cards print in that order. If Jira rejects the query, you see Jira's own error message, starting with "Jira didn't accept the query".
• Filter: search for and pick a Saved filter.
• Project: search for and pick a project. Newest issues come first.
• Issue keys: paste keys separated by spaces, commas, semicolons or new lines (for example ACME-12, ACME-15, OPS-3). Lowercase is fine and duplicates are dropped. Cards print in the order you pasted them. Anything that isn't an issue key is listed under Skipped (not issue keys). Up to 500 keys at a time.

Sprint, backlog, board and saved filter cards print in Jira's rank order.

Then choose what to print under Print:

• All matching issues
• Only issues I haven't printed yet
• New, plus issues changed since I printed them
• Include sub-tasks: on by default. Turn it off to leave sub-tasks out.
• Skip done issues: leaves out issues in a Done status category.

Click Load issues.

Corkprint reads Jira as you, so you only ever see and print issues you can already see in Jira.

Pick which cards to print

After loading, the Issues list shows every issue with a checkbox, plus how many are selected. Untick the ones you don't want, or use All and None. Only ticked issues appear in the preview and on paper. The header shows the source, how many cards are selected, the page count and, if you have printed this source before, when you last printed it.

Only print what's new

Corkprint remembers which issues you printed from each sprint, backlog, board, filter, project or JQL query. After you print or download a PDF, Corkprint asks whether the cards came out ("Did the 12 cards print?" or "Did you save the PDF with 12 cards?"). Click Yes, mark as printed to record the print, for the cards that were ticked when you clicked Print or Download PDF. Click Not printed if you cancelled the print dialog or didn't keep the PDF, and nothing is recorded. Your browser reports a cancelled print the same way as a finished one, so Corkprint never counts a print until you confirm it.

• Only issues I haven't printed yet hides every issue you printed from this source before. Use it during a running sprint to print just the issues added since you put the sprint on the wall.
• New, plus issues changed since I printed them also brings back issues that were updated in Jira after you printed them, for example after a refinement session.
• A notice tells you how many issues were printed before and are hidden.
• Forget what I printed (next to All and None) clears the history for that source, so every issue shows again.

History is per person: a teammate's prints don't hide anything for you. Pasted issue keys, selected issues from search and a single issue have no history, so all three modes print every issue for them.

Design the card

The 2. Card design tab has a list of fields and the card's four areas:

That is up to 13 fields on one card.

• Add a field: drag it from the field list onto an area, or use the + menu next to the field and pick the area. Dropping a field on Title replaces the current title field.
• Move a field: drag it to a new position or another area. Dragging a field onto the title swaps it with the current title.
• Remove a field: click × on it.

Each field on the card has its own settings:

• Text size: S, M, L or XL.
• B: bold.
• Aa: (Show the field name): prints the field's name before its value. Not on the title.
• ( ) (Outline (badge)): draws an outline around the value, as used for story points. Top and bottom rows only.
• lines (title and body lines): how many lines the text may take before it is cut off with an ellipsis, from 1 to 12.

Fields you can use: Key, Summary, Type, Status, Priority, Assignee, Reporter, Story points, Epic, Parent, Labels, Components, Fix versions, Due, Sprint, Team, Estimate, Project, Created, Updated, Description, and your site's custom fields, listed by name. Custom fields of type text, number, select list (including cascading), user, date, version, project and team can be printed, as can lists of those. Description prints a plain-text excerpt.

Story points are found automatically, whether your projects use "Story point estimate" or "Story Points". Epic shows the parent epic's name. Estimate is the original estimate in Jira's format (for example 1d 4h). Dates follow your browser's language: Oct 5, 2026 for US English, 5 Oct 2026 otherwise.

After you add a custom field to the design, click Load issues again to fetch its values.

Card style

• Color cards by: No color, Issue type, Priority, Project, Status, Epic, First label, First component or Assignee.
• Color style: Top band, Side strip, Light background or Colored border.
• Border: None, Thin, Thick or Dashed.
• Corners: Rounded or Square.
• QR code to the issue: Off, Top right, Bottom right or Bottom left.
• Text size: scales all text on the card from 70% to 150%.

When cards are colored, Colors (click a swatch to change it) lists each value among the loaded issues with a count. Click a swatch to pick a different color for that value. Reset colors goes back to the defaults. Issue types and priorities start with familiar colors (bugs red, stories green, highest priority dark red); other values get a fixed color from a print-friendly palette, so the same value gets the same color every time.

Text that doesn't fit is wrapped and cut off with an ellipsis, and nothing is printed over the QR code, so text never spills off a card.

QR codes

The QR code links to the issue on your Jira site (your site address followed by /browse/ and the issue key). Scan it with a phone camera to open the issue. The code contains nothing else and is generated in your browser.

Templates

The menu at the top of 2. Card design lists the templates. Four built-in templates come with every site:

• Sprint board: key and type on top, a large bold summary, the epic, then assignee and a story point badge. Colored by issue type with a QR code.
• Big title, wall readable: large key and story points, an extra-large summary and the assignee. Colored by priority as a side strip.
• Detail card (description): key, priority and due date, summary, a description excerpt, labels and components, then assignee, sprint and estimate. Colored by project with a QR code.
• Small label (key + summary): key, summary and a QR code, for small label stock.

Any change you make applies to the current print straight away, saved or not ("Unsaved changes. They apply to this print either way.").

• Save as new: enter a Template name and click Save template. The template is saved for everyone on your Jira site.
• Save: saves changes to a site template.
• Delete: deletes a site template for everyone.
• Make my default: the template selected when you open Corkprint. Each person picks their own.

Built-in templates can't be changed or deleted; use Save as new to keep your version. Save and Delete only appear for the person who created a template and for Jira admins. Everyone else can use the template and save a copy with Save as new. A site can have up to 200 saved templates. Saving and deleting templates need an active license; without one, Delete is disabled and you can still view and use your templates in the designer.

Paper and labels

On the 3. Paper and labels tab, choose a Paper:

• Plain paper, A4 and Plain paper, US Letter: 1, 2, 4, 6, 8, 9, 10 or 12 cards per page. Corkprint picks the page orientation and grid that make the cards closest to an index-card shape. Cut marks (on by default) adds small marks at each card's corners for cutting.
• Labels and index cards:
  • Avery 5163 / 8163 shipping labels, 2 x 4 in, 10 per Letter sheet
  • Avery 5164 / 8164 labels, 4 x 3 1/3 in, 6 per Letter sheet
  • Avery 5388 index cards, 3 x 5 in, 3 per Letter sheet
  • Avery L7165 labels, 99.1 x 67.7 mm, 8 per A4 sheet
  • Avery L7163 labels, 99.1 x 38.1 mm, 14 per A4 sheet
  • Index card 3 x 5 in, one per sheet (printer feeds the card)
  • Index card 4 x 6 in, one per sheet (printer feeds the card)

For label sheets, Start at label lets you use up a half-used sheet: printing starts at that position (shown as row and column) on the first page.

The tab also shows the card size in inches and millimeters. Your paper choice is remembered for next time. Until you choose, Corkprint starts with 6 cards per page on Letter for US English browsers and on A4 otherwise.

Getting labels to line up

• In the print dialog, set scale to 100% (Actual size), not "Fit to page".
• Set margins to None if your browser offers it.
• Make sure the paper size in the dialog matches the stock (Letter or A4).
• Print one page on plain paper first and hold it against a label sheet.

Print or download a PDF

• Print opens your browser's print dialog with only the cards, one sheet per page at the right paper size. You can also choose "Save as PDF" there.
• Download PDF saves a file named after the source and the date, for example Corkprint-This-sprint-2026-10-01.pdf, ready to send to a print shop.

When the print dialog closes or the PDF is handed to your browser, a bar asks whether the cards came out. Only Yes, mark as printed adds them to your print history (see Only print what's new); Not printed discards the print.

The preview shows up to 12 pages at a time; use Previous and Next to page through longer prints.

The PDF download uses the standard PDF fonts, which cover English and Western European characters. If your cards contain other scripts (for example Cyrillic, Greek, Chinese, Japanese or Arabic), Corkprint tells you, and those characters show as "?" in the downloaded PDF. Use Print and choose "Save as PDF" to keep them; the print dialog prints every script.

Licensing and trials

Corkprint is paid through Atlassian, with a 30-day free trial.

Pricing is graduated: from 11 users every user is billed, each band at its own rate. Annual billing is 10 times the monthly price.

If the license is not active, Corkprint shows "This site has no active Corkprint license. Ask a Jira admin to renew it in Apps > Manage apps." Load issues, Print and Download PDF are disabled, and saving or deleting templates is refused. Your saved templates, preferences and print history are kept and come back when the license is renewed.

Permissions and data

• Corkprint runs on Atlassian's Forge platform and sends nothing to any outside server. The app has no external network permissions.
• It reads Jira as the signed-in person: issues, boards, sprints, saved filters, projects and field definitions. It never changes anything in Jira.
• Cards, the preview, PDFs and QR codes are made in your browser. Printing goes from your browser to your printer.
• Corkprint stores, in Forge storage for your site:
  • templates (name, layout, colors, border and QR settings, the creator's Atlassian account id, last change time), shared with everyone on the site;
  • your preferences (default template, paper choice), per person;
  • your print history per source (issue keys and each issue's last-updated time when you printed, and when you printed), per person, up to the 5,000 most recent keys per source.
• Issue content (summaries, descriptions, field values) is never stored.
• Stored data stays until you delete it in the app (Delete for templates, Forget what I printed for history) or the app is uninstalled.

Limits and known gaps

• Up to 1,000 issues per print. If a source has more, Corkprint shows the first 1,000 and tells you to narrow the query.
• Up to 500 pasted issue keys at a time.
• The PDF download covers Western European characters only; use Print and "Save as PDF" for other scripts.
• Label alignment depends on printing at 100% scale.
• Corkprint prints from Jira. It doesn't update Jira from paper cards, and it doesn't print Confluence pages.
• Date format follows your browser's language and can't be changed in the app.

FAQ

Can I print the backlog, or just some of the cards? Yes. Use Print backlog cards in the backlog menu, or Print cards on issues you select in search. Every issue gets a checkbox before you print, and you can skip sub-tasks and done issues.

Can I fit several cards on one page? Yes. 1, 2, 4, 6, 8, 9, 10 or 12 cards per A4 or Letter page, with cut marks, or Avery label and index-card stock.

Does the preview match what prints? Yes. The preview is drawn with the same layout and font measurements as the printout and the PDF, so what you see is what you get.

Can I show more than a few fields on a card? Yes. Up to 13 fields, including custom fields, story points, epic, sprint, team, estimate and a description excerpt.

Can I style the cards? Yes. Color by issue type, priority, project, status, epic, label, component or assignee as a top band, side strip, light background or colored border, change any color, and choose borders, corners and text sizes.

Do I have to reprint the whole sprint after a change? No. Use Only issues I haven't printed yet or New, plus issues changed since I printed them.

Will it handle a big sprint? Corkprint loads up to 1,000 issues per print, page by page, and tells you if a source has more.

Can my whole team use the same card design? Yes. Saved templates are shared across the site. Only the creator or a Jira admin can change or delete one, and each person picks their own default.

Is my data sent anywhere? No. Corkprint runs on Atlassian and makes cards, PDFs and QR codes in your browser.

Uninstalling and your data

Printed cards and downloaded PDFs are yours and are not affected. When the app is uninstalled, Atlassian deletes Corkprint's stored templates, preferences and print history for your site.

Support

Open a request in the Great Work support portal (linked from the Marketplace listing) or email hello@greatwork.company. First response within 1 business day.