Jira → Google Sheets, with your notes kept

Many teams keep a report in a spreadsheet: a Jira filter on the left, the team’s own notes on the right (“waiting on the client”, “switch this ticket to Ben”). Jira’s free add-on refreshes the data by overwriting it, so the notes drift onto the wrong rows. This app keeps them in line.

What it does

• Keeps a Jira filter up to date in a Google spreadsheet you pick. Changes in Jira reach the sheet within minutes. Start from one of your saved Jira filters, or type the JQL. A report can follow its saved filter: when someone changes the filter in Jira, the report follows within the hour.
• Keeps each row tied to its issue key. An issue that changes is updated in its own row, wherever you sorted it. New issues are added at the bottom. An issue that leaves the filter keeps its row, marked “Not in filter since” and the date, so your note isn’t lost; Clean up removes such rows when you ask, or a report can remove them by itself.
• Never writes in your columns. Everything to the right of the app’s columns is yours: notes, formulas, colours, cell comments. A formula you keep beside the issues is copied into the rows of new issues, so your calculations cover them too.
• Each issue key links to the issue in Jira.
• Shows the columns you choose: any Jira field, including custom fields, sprints and story points, plus the latest comment, the comment count, issue links, “In current status since”, “Last change”, the parent’s summary and the status category. Time tracking shows in hours. A saved filter brings the columns it shows in Jira.
• Logs every change in a second tab (“… changes”): each step of each field, when it happened and who made it, from Jira’s own history. “Status: To Do → In Progress, Anna”, then “In Progress → Done, Ben”.
• Time in status and cycle time: columns for when work started, the cycle time in days and how often an issue was reopened, and, if you want it, a tab with the days each issue spent in each status.
• A Summary tab, if you want one: issues and story points per status, assignee, priority and type, with charts. It is written once, as live formulas over the report, and then it’s yours to change.
• A daily trend, if you want one: a small tab gets one row a day per status, ready for a chart of whether the backlog grows.
• Save a copy of the tab in one click, for example at the end of a sprint.
• Headers in row 1, if your charts or tools need it. By default row 1 says when the report was last updated and links to its filter; you can choose to put the headers there instead.
• Several reports per site, each in its own tab: one workbook can hold a tab per team or per release.
• Tells you when it stops. If an update can’t run (a Google sign-in was removed, the spreadsheet went to the bin), the report shows what to do, and its owner gets one email, as can the Jira groups you choose. A safety hold stops an update that would suddenly mark most rows as gone, until you confirm.

For teams

• Share a report with your Jira groups or the whole site. Colleagues see its state and can update it now; only its owner changes it.
• When someone leaves, a colleague or a Jira admin can take their report over, so the sheet keeps updating.
• Jira admins get a settings page in Jira settings → Apps: every report on the site, who may add reports, how they may be shared, the defaults new reports start with, and an activity log of who did what.

How your data is handled

The app runs on Atlassian Forge, inside Atlassian’s cloud. Each report reads Jira as the person who set it up, so the sheet never shows more than they may see in Jira, and no Jira password or token is stored. Google access is limited to the files you pick with Google’s own file picker, so the app can’t see the rest of your Drive.

Who can open the spreadsheet is set in Google, with its Share button: anyone who can open it sees the issues the report shows, even ones they can’t open in Jira. Details are in the privacy policy.

For security-minded teams, a Jira admin can limit who uses the app, which Google accounts may receive Jira data, how far a report’s spreadsheet may be shared, and which fields never leave Jira: see Security and data safety.

What it doesn’t do

• It doesn’t write back to Jira. Notes in the spreadsheet stay in the spreadsheet.
• It works with Jira Cloud only, not Jira Data Center.
• Excel Online is not supported yet.

Next

Set it up in about two minutes, or read the help pages in the menu.