Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Who commented, who changed, who moved it: 3 Argon functions that turn Jira history into answers

 

The gap in native JQL

Every Jira issue has a hidden layer: the comments, the field edits, the status moves. That's where the real decisions live — "approved," "blocked," "reopened," "priority bumped." Native JQL can't search any of it. You end up clicking through changelogs one issue at a time.

 

Native JQL shows you the current state of an issue. It can't tell you who said what in a comment, who edited a field, or who actually pushed a ticket to "Done." Argon's commented, changedBy, and transitionedBy functions answer all three — each in a single line of JQL.

JQL Argon  adds three functions that close this gap. Here's the advantage each one gives you:

 

1. commented — search what people actually said

Advantage: Turn comment threads into a searchable audit trail — by author, date, and keyword. No more scrolling through tickets to find who approved or flagged something.

      issue in commented("project = DEV", "", "2023/01/01", "2026/08/01")

Every issue in DEV with a comment in that window — including the exact comment, its author, and when it was posted (or edited).

 

3-1bb.jpg

 

 

2. changedBy — search what fields actually changed

Advantage: Prove what changed, when, and who touched it — for any field, not just status. Ideal for audits, sprint reviews, and answering "did anyone update Priority last month?" without digging through the changelog manually.

     issue in changedBy("project = DEV", "Priority", "2026/01/01", "2026/04/13", "jsmith")

Every issue in DEV where user changed the Priority field in that window — scoped accountability, in one line.

 

x2.jpg

 

 

3. transitionedBy — search what actually moved, not just what's showing now

Advantage: See the real workflow history — who moved an issue to a given status and when — instead of just its current state. Perfect for sprint retros ("what was actually closed this sprint") and compliance ("who approved this, and in what order").

      issue in transitionedBy("project = SER", "Done", "2023/01/01", "2023/12/31", "jsmith")

Finding issues transitioned to "Done" by jsmith user.

 

Why this matters

  • Audit & compliance — prove who said, changed, or approved what, and when
  • Sprint retrospectives — see what was actually said, edited, and completed in the window that matters
  • Accountability without blame — visibility into real activity, not just current state
  • Zero setup — all three run directly in the standard Jira search bar, on Atlassian Forge, so your data never leaves Atlassian

Each function also supports not in — flip any query to find what didn't happen: comments that never came, fields never touched, statuses never reached.

 

Enjoy!

Bartek from Orbiscend OU (JQL Argon app provider).

 

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events