Bulk Comments for Jira

Installation

Installing takes about a minute and needs a Jira Cloud site admin, since apps are installed site-wide.

1. Open Bulk Comments for Jira on the Atlassian Marketplace, or search for it from Apps → Explore more apps inside Jira.
2. Click Try it free and choose your Jira Cloud site.
3. Accept the permissions it asks for: read and write Jira work items, read Jira user profiles, and app storage. Nothing else is requested — see Permissions Required for what each one does.
4. Open it from Apps in the left sidebar, or from any issue's ••• actions menu and Activity panel.

Removing the app is just as clean. Uninstalling from Apps → Manage apps deletes everything it stored, and comments already posted stay on their tickets as ordinary Jira comments.

Overview

Bulk Comments for Jira is an Atlassian Forge app installed directly inside Jira Cloud. Pick up to 25 tickets, then give each one its own comment and its own status change — or write one comment that goes to all of them, or copy a comment that already exists onto every ticket, media and all. Everything happens on one page, in three steps.

The Full Guide below walks through each step with screenshots.

No context switching: Everything happens inside Jira. There's no external server in the data path — comments and media move between Jira tickets through Atlassian's own infrastructure.

Limits

Three numbers govern how much one send can carry. They are independent of each other, so a batch can sit comfortably inside two of them and still be refused by the third.

Why the total is bigger than it looks

Attachments in Jira belong to an issue, not to a comment, so a file you send to 9 tickets is written 9 times. The figure that counts against the 2 GB ceiling is therefore file size × ticket count, not the size of what you attached.

A worked example: four 120 MB videos is 480 MB in the editor, and every file is well inside the 150 MB per-file limit. Send that to 5 tickets and Jira receives 2400 MB — over the ceiling, and the send is refused. Send it to 4 tickets instead and it is 1920 MB, which goes.

If your Jira site sets a lower attachment limit than 150 MB, that one wins — the app reads your site’s real limit and checks against it. Jira’s own instance-wide storage quota is separate again and is not something the app can see; if you hit that, see Files and uploads in Troubleshooting.

Full Guide

Where to open it from

Three places, doing deliberately different jobs:

• The left sidebar → Bulk Comments for Jira — the full app, starting at the Tickets step with nothing selected.
• An issue’s ••• actions menu → Bulk Comments — opens the full app at the Tickets step with that ticket already selected, so you carry on picking the rest. Everything the app can do is there.
• An issue’s Activity panel → Bulk Comments tab — sits under the comment history and auto-selects that ticket’s most recent comment, so you can copy it, media and all, onto other tickets without leaving the page.

Step 1 — Choosing tickets

Search by keyword or issue key, or paste a key straight in. Two modes sit beside the field: Basic for plain search and JQL when you want a precise query.

Narrow what comes back with:

• Project — one project, or all of them.
• Status — tick the statuses you want to see. The names are read from the projects in your results, so you get your own workflow’s wording — “In Review”, “To Doo” — rather than generic categories. Done work is hidden by default; one tick brings it back.
• Sort — Updated (most recently changed), Ticket key, or Summary (alphabetical). The arrow beside it flips between ascending and descending.

Select all visible ticks every ticket currently on screen, and pressing it again clears them. Select up to 25 in total.

The tray along the bottom lists every ticket you have picked, no matter which search you found it in — so a selection built from three different queries is still visible in one place. Press the × on any chip to drop that ticket without going back to hunt for it.

This is always the first step, whether you go on to write a comment or copy one.

Step 2 — Writing a comment

Two ways to fill the tickets you picked, both on the same page. Mix them freely — a shared comment on most tickets and its own on a few is still one send.

One comment for all

Write it once and every selected ticket gets it: same text, same formatting, same attachments, including images, videos and files of up to 150 MB each.

A different comment per ticket

Click any ticket in the list and it opens on the right with everything you need in order to write about it — its description, its details, its attachments, and every comment already on it. You are not writing blind into a key you half remember.

Images in those existing comments open inside the app. Videos and other files open the comment on its own ticket in a new tab instead, so you view them in Jira’s own viewer rather than a lesser copy of it.

Attachments on the comment you are writing work the same as anywhere else, up to 150 MB per file — see The comment editor.

Settings — how the panel opens

The Settings button in the top-right of the Comment step controls one thing: which of the ticket panel’s collapsible sections are already expanded when you open a ticket.

• Description — the ticket body.
• Details — people, dates, subtasks and custom fields.
• Attachments — loads previews when opened.

All three start expanded. The right answer depends on the work: triaging bugs, you want the description every time; running a status sweep across 25 tickets you already know what they are, and you want the writing surface at the top instead. Collapse what you don’t need and the choice sticks — it is remembered for every batch after, not just this one.

Ready, or skipped

Every ticket in the list carries a badge, and it decides whether that ticket is part of the send. Not written means nothing has happened to it yet. Open it and give it a comment, an attachment or a status change and the badge flips to Ready — own; take the shared comment instead and it reads Ready — shared.

A ticket still reading Not written when you send is skipped — nothing is posted to it and nothing happens to it. The footer counts both, so “2 ready · 3 skipped” tells you exactly what is about to go out before you press anything.

Changing a ticket’s status

Open any ticket in the list and you can move it at the same time as commenting on it — Set DTB-8 from To Do to… sits directly above its comment box. Each ticket moves independently: one to In Review, the next to Done, and the rest left alone. The options come from that ticket’s own workflow, so you only ever see transitions Jira would accept.

A status change can travel on its own. A ticket with a new status and no comment still counts as ready and is included in the send — it is not treated as a blank row and skipped.

Starting over — Clear all

Clear all sits above the ticket list and wipes the work rather than the selection: every comment you have written, the shared one included, and every status change you have queued. It asks first — the button changes to Clear comments & statuses? and needs a second click, so a stray press costs nothing.

What it deliberately does not do is send you back to the Tickets step. The tickets you picked stay picked, so this is the fast way to rewrite a batch from scratch without hunting down the same 25 issues a second time. Nothing has been posted to Jira at this point, so there is nothing to undo — clearing only affects what is on screen.

Attachments work the same way here as anywhere else in the editor — see The comment editor for how files are attached, sized and uploaded.

Step 2 — Or copy a comment that already exists

Open the source ticket in another tab, copy the link to the comment you want, and paste it into the app. Every ticket in the list below gets a copy of it — text, formatting, images, video and file attachments, exactly as-is.

You need two things: the tickets that should receive it, and a link to the comment being copied. The order is up to you. Grab the link from the source ticket first and then open the app, or open the app, pick your tickets, and fetch the link from another tab when you get to it.

Either way it lands in the same place: select the tickets in the Tickets step, then on the Comment step switch from Write a comment to Copy a comment and paste the link there. Send behaves exactly as it does for a comment you wrote.

You don’t have to memorise any of this. Switching to Copy a comment puts the whole procedure on screen, worked example included — and the Copy to n tickets button stays disabled until what you paste is actually a comment link:

The only part that happens outside the app is step 1. The link icon appears when you hover a comment in Jira, tucked beside the author’s name — it is easy to miss:

The comment editor

Everything you write is posted as native Jira formatting, so a comment sent from here is indistinguishable from one typed into Jira itself — same headings, same tables, same code blocks, same file cards. The toolbar and the keyboard shortcuts deliberately mirror Jira's own editor, so there is nothing new to learn.

Shortcuts below are written in Mac notation. On Windows and Linux read ⌘ as Ctrl, ⇧ as Shift and ⌥ as Alt. The app detects your machine and shows the right one in every tooltip.

Headings

The dropdown at the far left of the toolbar sets the current block. It shows what you are currently in, so you can always tell whether the cursor is inside a heading.

Text formatting

Lists, quotes and dividers

Tables

The table button opens a size grid — drag across it to choose how many rows and columns you want. Once the cursor is inside a table, a second row of controls appears with everything you need to reshape it:

• Header row and Header col — toggle either independently, so a table can have a header row, a header column, both, or neither.
• Add columns before or after the current one, and add rows above or below.
• Delete table to remove the whole thing in one click.

Code blocks

A code block keeps your indentation and monospacing intact, and carries a language selector with 42 languages — Bash, C, C++, C#, CSS, Dart, Go, GraphQL, Groovy, Haskell, HTML, Java, JavaScript, JSON, Kotlin, Python, Ruby, Rust, SQL, TypeScript, YAML and more, plus (None) for plain text. The language travels with the comment, so Jira highlights it correctly on every ticket you post to.

Slash commands

Type / anywhere in the editor to open a command palette, exactly like Jira's. Keep typing to filter the list, move with the arrow keys, and press Enter to insert. Twelve commands are available, so you never have to reach for the toolbar mid-sentence:

It matches on synonyms, not just labels. The attachment command is called “Image, video, or file”, but /screenshot, /upload, /photo and /media all find it too.

Mentions, links and emoji

• @mentions — type @ and search your Jira users. Mentioned people are notified on every ticket the comment lands on, which is why a send containing a mention always asks you to confirm first.
• Smart links — paste a Jira or Confluence URL and it converts into a live link card showing the item's title, status, priority and assignee, fetched fresh rather than frozen at paste time.
• Emoji — browse from the toolbar or type /emoji.

Attachments

Attach files three ways: drag them into the editor, paste a screenshot straight from the clipboard, or use the toolbar button. Dropping a file places it where your pointer is, not where the cursor happened to be.

• Up to 150 MB per file, with no limit on how many files one comment can carry. If your Jira site sets a lower attachment limit, that one wins — the app reads the site's real limit and checks against it the moment you attach, so an oversized file is refused immediately rather than after you have written the comment.
• Uploading starts on attach, not on Send. The file moves while you are still typing, so the send itself is usually near-instant. Nothing is visible on any ticket until you actually send, and anything you attach and then delete is discarded.
• Images and video preview inline, align left, centre or right, and resize by dragging the edge — the same handles Jira gives you. PDFs and other documents post as file cards.
• Large files are copied per ticket in the background, so a long video posting to 25 tickets never stalls or times out the batch.
• A whole send is capped at 2 GB, counted across every ticket in the batch rather than per ticket. That is a separate ceiling from the 150 MB per file, so a batch can go over the total while every individual file sits well inside its own limit — four 120 MB files going to 5 tickets is 2400 MB and will not send. Nothing is posted when it trips; split the tickets across two sends and the total resets. See Files and uploads in Troubleshooting.

Step 3 — Sending and delivery

The Send step tracks every ticket individually and posts them in parallel, so a batch of 25 goes out together rather than one after another. Three counters — Delivered, Sending, Failed — update live above a row for every ticket, and each row links straight to the comment on its issue. When the run finishes the heading changes to Comments posted and tells you how long it took.

Anything that fails gets a Retry n failed button that re-runs only those tickets, leaving the delivered ones untouched.

Every row opens its ticket: click the ticket key or the ↗ on the right and it opens in a new tab — scroll to the bottom of the ticket to see the comment or the change that landed.

Undo is one click, and it undoes the whole run. Undo — delete comments and files removes the comments that send posted and the files it uploaded, freeing that storage again. Files that were already on a ticket beforehand are left alone.

Light and dark

There is no theme setting to find, because the app does not have a theme of its own. It renders in whichever colour scheme Jira hands it, so it is light when your Jira is light and dark when your Jira is dark — including the comment editor, the status lozenges and the readiness badges, which are tinted for each scheme rather than inverted.

Every screen in this guide looks like this in dark:

Support & Contact

For technical support, feature requests, or general questions about Bulk Comments for Jira:

• Email: support@datapingo.com
• Response Time: Within one business day
• Support Scope: App functionality, configuration, and technical issues