Comment Fields for Jira
Overview
Comment Fields for Jira is an Atlassian Forge app for Jira Cloud, developed by qadram S.L.U.
It solves a simple problem: Jira doesn't natively expose an issue's first comment, last comment, or total comment count as fields you can see in a list, filter by, or export. This app reads issue comments and writes that information into three read-only custom fields, and lets you export the current search results (including a comment table) to Excel.
Because it runs on Atlassian Forge, all processing happens inside Atlassian Cloud — no data is sent to qadram's own servers.
Key Features
| Feature | Description |
|---|---|
| First comment field | Read-only custom field showing the content of the first comment on an issue. |
| Last comment field | Read-only custom field showing the content of the most recent comment on an issue. |
| All comments count field | Read-only custom field showing the total number of comments on an issue. |
| Site-wide sync | Jira admins can trigger a sync across the site to (re)populate the fields for all issues. |
| Excel export | Any user can export the current JQL search result to an Excel file, including standard issue fields plus a comment table. |
How It Works
The app reads comment data from issues: author display name, comment creation time, and comment body (extracted as plain text from Atlassian Document Format). 2.
It writes that data into the three custom fields listed above. 3.
Sync progress (counts, timestamps, pagination token) is stored in Forge Key-Value Storage, scoped to your Jira site — this is operational data only, never used for advertising or shared externally. 4.
When exporting to Excel, the app also pulls: issue type, key, ID, summary, reporter display name, priority, status, created date, and updated date.
Installation
Go to Jira Settings → Apps → Find new apps. 2.
Search for "Comment Fields for Jira". 3.
Click Get app / Install. 4.
Review and accept the requested permissions (see section below). 5.
Once installed, add the three custom fields to the relevant screens (see next section).
Adding the Fields to Your Screens
After installation, the three fields (First comment, Last comment, All comments count) need to be added to your project's screens/field configuration like any other custom field:
Go to Jira Settings → Issues → Custom fields. 2.
Locate the three fields created by the app. 3.
Add them to the screen(s) and/or board/backlog views where you want them visible. 4.
Optionally add them as columns in your issue navigator or filters.
These fields are read-only — users cannot manually edit their values; they are only updated by the app's sync process.
Using the App
Running a Site-Wide Sync (Admins)
Jira admins can trigger a sync that scans issues across the site and (re)populates the three custom fields based on current comment data. This is useful:
Right after installing the app, to backfill existing issues.
Periodically, if you want the fields refreshed beyond normal update triggers.
Exporting Search Results to Excel (All Users)
Any user can export the current JQL/filter result to an Excel (.xlsx) file. The export includes:
Standard issue fields: type, key, ID, summary, reporter, priority, status, created, updated.
A comment table per issue (author, timestamp, comment text).
Typical use cases: audits, reporting to stakeholders who don't have Jira access, or offline analysis.
Permissions & Data Handling
The app requests the following OAuth scopes:
| Scope | Purpose |
|---|---|
read:jira-work | Read issue and comment data. |
write:jira-work | Write values into the app's custom fields. |
write:app-data:jira | Store app-specific configuration/data. |
storage:app | Store sync progress in Forge Key-Value Storage. |
Data residency and processing:
All processing runs on the Atlassian Forge platform ("Runs on Atlassian").
No data is transmitted to qadram's own servers.
No account passwords are ever collected.
Data stays within the Atlassian Cloud region associated with your site.
qadram does not sell personal data and shares it with no third party other than Atlassian (which hosts Jira Cloud/Forge, and handles Marketplace billing/trials).
Legal basis: qadram acts as a data processor; the installing organization (your company, as site admin) remains the data controller of your Jira content.
For the full legal text, see the Privacy Policy
Data Retention
Custom field values and comments follow your organization's normal Jira retention policy.
Sync status data in Forge storage persists for your installation until it's overwritten, the app is uninstalled, or Atlassian deletes installation data (typically after Atlassian's standard uninstall retention window).
Uninstalling the app removes the app's custom fields from Jira after Atlassian's standard removal period.
Uninstalling the App
Go to Jira Settings → Apps → Manage apps. 2.
Find Comment Fields for Jira. 3.
Click Uninstall. 4.
The app's custom fields will be removed from your screens after Atlassian's standard retention period.
Troubleshooting
Suggested starting points:
Fields show no data: Run a site-wide sync (admin) to backfill existing issues.
Excel export missing comments: Confirm the issue actually has comments and that your JQL filter includes the expected issues.
Permission errors: Confirm the app's OAuth scopes were approved during installation by a site admin.
Support & Contact
Vendor: qadram S.L.U.
Website: branchcreation.com
Support email: support@branchcreation.com
For end users with questions or data requests, contact your Jira site admin first; admins can uninstall the app, remove fields from screens, or use Jira/Atlassian's built-in data-subject tools.