Searchable Fields for Jira

Search and sort Jira work items by last comment date, last comment author, comment count and subtask counts. The app adds five read-only fields you can use in ordinary JQL and as columns in work item search.


What the app adds

Five read-only custom fields on Jira work items:

  • Last comment date (date and time) — creation time of the most recent comment without a visibility restriction
  • Last comment author (user) — author of that comment
  • Comment count (number) — number of comments without a visibility restriction
  • Subtask count (number) — number of subtasks of the work item
  • Open subtask count (number) — subtasks that are not in the Done status category

The app does not store comment text. Jira includes comment text in the data the app fetches, but the app only uses each comment's creation time, author and visibility setting.

Search with JQL

Use the field name in quotes:

"Comment count" = 0
"Last comment author" = currentUser()
"Last comment date" < startOfDay(-7)
"Subtask count" > 0 AND "Open subtask count" = 0

The fields have no short JQL alias. Use the names above.

How to try it: In Jira, open the work item search, switch to JQL, paste "Comment count" = 0, and run the search. You should see work items that have no unrestricted comments (or none at all).

Show the fields as columns

In the work item search (Issue Navigator), open the column picker and add any of the five fields.

How to try it: In the same search, open the column picker, type "comment" or "subtask", and tick Last comment date, Last comment author, Comment count, Subtask count or Open subtask count. The values should appear as columns. In our tests the fields appeared on a company-managed and a team-managed project, without screen setup.

When values update

The fields update when someone:

  • adds or deletes a comment,
  • creates or deletes a subtask,
  • changes a subtask's status, moves it to another parent, or changes a work item's type.

Updates usually arrive within seconds. Atlassian allows event delivery to take several minutes, so a value can lag.

Editing an older comment does not change Last comment date. Deleting the last comment moves the date and author back to the previous comment. If no comments remain, the date and author are empty and the count is 0.

How to try it: Open a work item that you can comment on and note its Comment count and Last comment date. Add a comment that is not restricted to a role or group. Within a few seconds (sometimes longer), Comment count should increase by 1 and Last comment date and Last comment author should match the comment you just added.

Fill the fields on existing work items

Work items created before the app was installed start empty. To fill them:

  1. In Jira, go to Settings > Jira admin settings > Marketplace apps > Apps and open Searchable Fields (Jira administrators only).
  2. Click Build for existing work items.
  3. The page shows progress and refreshes every 10 seconds. Click Stop to stop after the current page.

The build covers every work item the app can see. In our test, a full build of 48,584 issues took about 1.5 hours.

How to try it: As a Jira administrator, open the Searchable Fields admin page, click Build for existing work items, and wait until the progress figure moves. Click Stop if you only want a short run. Then search for a work item that existed before the app was installed and check that the five fields have values (or 0 / empty, if it has no unrestricted comments and no subtasks).

Known limitations

  • Restricted comments (visible to a role or group only) are not counted and never become the last comment.
  • In Jira Service Management, internal comments are counted, because Jira does not mark them with a visibility restriction.
  • When a work item changes type to or from a subtask, the old parent is not recalculated until its next change or the next build.
  • If the app license is not active, the fields stop updating and the build stops.

Uninstalling

When you uninstall the app, the five fields disappear from Jira. The app does not remove the values itself. If you reinstall within 30 days, the fields and their values come back. In our test, reinstalling right away kept the values. After 30 days, Atlassian permanently deletes the field data. The app's build status in Forge hosted storage is deleted by Atlassian under the Forge hosted storage lifecycle.

Privacy and security

The app sends no data out of Atlassian. It has three scopes (read:jira-work, write:app-data:jira, storage:app), no admin scopes and no remotes. The only personal data it stores is the Atlassian account ID in the Last comment author field, on the work item. Comment text is not stored. Logs contain only the type of operation, counts and fixed error keys. Never comment text, names or account IDs.

See the privacy policy at https://www.helkrypt.no/privacy/apps (section 4.9).

The app qualifies for Runs on Atlassian. Whether it follows the site's data residency setting has not been confirmed yet.

Support

FAQ

Can't I do this with Jira Automation?

Partly. Atlassian's workaround is a custom field plus an Automation rule per value. You set it up yourself, older work items are not filled unless you add a backfill, and we found no documented smart value for open subtask count.

Does it count restricted comments?

No. Comments restricted to a role or group are not counted. In Jira Service Management, internal comments are counted, because Jira does not mark them with a visibility restriction.

Does it add entries to the work item history?

No. The app writes its fields without a changelog entry. We have not measured notifications.

Which projects does it work on?

It was tested on a company-managed and a team-managed Jira project, where the fields appeared in the column picker without screen setup. We do not claim it for every project type.

What happens if I uninstall the app?

The app does not remove the field values itself. According to Atlassian's lifecycle for Forge custom fields, the fields disappear from Jira when the app is uninstalled. If you reinstall within 30 days, the fields and their values come back. After 30 days, the field data is permanently lost.