Last Comment for Jira
See the newest comment of every issue as a column, search it with JQL and export it, without opening a single issue.
A read-only Last comment field: who wrote the newest comment, when, and what it says. Add it as a column, filter and sort with JQL, export it to CSV. Restricted comments stay private. Runs entirely on Atlassian.
What it does
- A column in issue lists and filters, part of CSV exports
- JQL on the text, the author and the date of the newest comment
- Sorting by the time of the newest comment
- Comments restricted to a role or group never appear; optionally only comments customers can see
- Fill for existing issues by preset or JQL, with pause and continue
- No notifications and no history entries
Where it appears
- The Last comment field: in issue lists, filters, JQL and CSV exports, and on issues where it is added to the layout.
- Settings > Apps > Last comment: JQL examples, which comments count, and the fill for existing issues.
How to use it
- Open Settings > Apps > Last comment and start a fill. The first option covers issues updated in the last 90 days.
- In any issue list or filter, add the Last comment column.
- Try the JQL examples on the admin page, for example "Last comment".Author = currentUser().
- New, edited and deleted comments update the field within a few minutes.
Permissions
The app runs on Atlassian’s Forge platform and declares no permission to contact outside servers. It asks for these scopes:
| Scope | Why |
|---|---|
| read:jira-work | Read issues and their comments to find the newest one, and run the JQL an admin enters for the fill. |
| write:app-data:jira | Write the Last comment field, which belongs to the app. |
| storage:app | Keep the settings and the progress of the fill in the app's storage on Atlassian's platform. |
Data and privacy
- What the app stores
- Which comments count, the id of the field, and the progress of the current fill. The newest comment itself is in the Jira field, inside Jira.
- Personal data
- None in the app’s storage. The field holds the comment author’s account id, as Jira’s own comments do; Jira shows the name.
- Logs
- Error messages only, without comment text.
- Where it lives
- In the app’s storage on Atlassian’s Forge platform, in the same data residency location as your Atlassian site. Nothing is copied to servers outside Atlassian. When the app is uninstalled, Atlassian deletes its storage under Atlassian’s data retention policy.
Details for all apps are in the privacy policy.
Good to know
- The field updates within a few minutes of a comment: Jira delivers comment events to apps with up to three minutes’ delay.
- Comments restricted to a role or group are never shown; the field shows the newest comment everyone who can see the issue can read.
- The text is kept up to 1,000 characters; the column shows the first 140.
Questions
No. Comments restricted to a role or group never reach the field, so it never shows more than a person can read on the issue.
No. The app writes the field without notifications and without entries in the issue history.
No. The field is updated in the background after each comment, and the fill runs on Forge’s queue, pausing by itself when Jira asks it to slow down.