The Scenario
A client handoff is happening next week and the client services lead needs to compile the full comment thread from 20 support tickets before the transition meeting. The issue keys are already in a Google Sheet. What she doesn't have is a way to extract every comment from every ticket without clicking into each one and reading — then retyping — who said what and when.
The bad version:
- Open Jira, navigate to the first issue key.
- Click the comment section, read through the thread, copy the most recent comment, paste it into a new sheet tab.
- Go back, find the next issue key, repeat.
- Realize halfway through that the client wants all comments, not just the last one, so go back to the beginning.
Twenty tickets with an average of four comments each is eighty comment entries to transcribe. The client handoff is in four days and there are three other things on the handoff checklist that actually require judgment.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your Google Sheet. It reads the Tickets sheet and through the Jira integration fetches every comment from every issue in one shot.
For each issue key in column A of my Tickets sheet, fetch all Jira comments and write the comment author, date, and body text into a new tab called Comments, with one row per comment.
What You Get
- A new Comments tab created with one row per comment across all tickets.
- Issue key, comment author, comment date, and comment body text in separate columns.
- Comments appear in the order Jira returns them — oldest first within each issue.
- Issues with no comments produce no rows, keeping the output clean.
What If the Data Is Not Quite Ready
You want comments from a specific date range only
The client only needs comments posted after the last billing milestone — anything before March 1 is out of scope.
For each issue key in column A of my Tickets sheet, fetch all Jira comments posted on or after March 1, 2025, and write the issue key, author, date, and body into a new tab called Comments.
The comment body text has internal @ mentions and markup that shouldn't go to the client
Jira comments include @mention syntax and internal formatting that looks messy in a plain sheet export.
For each issue key in column A, fetch all Jira comments. Strip @mention syntax and any internal formatting tags from the comment body before writing issue key, author, date, and cleaned body into a new Comments tab.
You want a per-issue comment count in the original Tickets sheet alongside the raw export
The Tickets sheet should show how many comments each issue has so the lead can see which tickets had the most back-and-forth.
For each issue key in column A of my Tickets sheet, fetch all Jira comments. Write issue key, author, date, and body into a new Comments tab. Also write the total comment count for each issue back into column B of the Tickets sheet.
Kill chain: fetch comments, filter internal notes, deduplicate repeated content, and format for client
For each issue key in column A of my Tickets sheet, fetch all Jira comments. Remove any comment from an author whose email ends in @ourcompany.com — those are internal notes. Remove duplicate body text where the same message was posted twice. Clean formatting markup. Write the remaining comments into a new tab called Client Comments with columns: issue key, author name, date, comment. Add a cover row in row 1 with column headers.
The filter, dedup, and formatting pass run together so the output goes directly to the client doc without a manual review step.
Try It
Get the 7-day free trial of SheetXAI and open a Google Sheet with your Jira issue keys listed in column A, then ask it to pull every comment thread into a separate tab formatted for sharing. See also: how to post batch comments to Jira issues and how to export open bugs for triage.