Forums

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

Decisions are hidden in comments - JQL advanced search

Most Jira decisions are hidden in comments. Are you agree?

▪️ Approvals.
▪️ Clarifications.
▪️ Stakeholder feedback.
▪️ Blockers.

They’re all there — but finding them later can be surprisingly hard.
On social media, the real discussion always happens in the comments.

The same is true in Jira.

But what if you could search those conversations just like you search issues?
With JQL Argon’s commented function, you can find issues based on:
▪ who commented
▪ when the comment was added
▪ what was written in the comment

Zrzut ekranu 1.04   3.jpg

This turns Jira comments from a passive activity log into a powerful searchable collaboration layer.

For example, you can search for:
• issues where a specific person commented,
• comments created in a specific time range,
• issues where a keyword appeared in the discussion

 

5.jpg

 

Suddenly, decisions hidden in comment threads become easy to find.
Because in project management — just like on social media — the comments tell the real story.

You can easily verify it yourself — just check out our app from Marketplace:

JQL Argon  


I'm curious:
How does your team search decisions hidden in Jira comments today?

 

Greetings

Bartek from Orbiscend OU (JQL Argon app provider)

 

 

4 comments

Nadir Jabbarli
Contributor
April 1, 2026

Thanks for sharing this — very interesting perspective 👏

I tried to reproduce your example, but I ran into an issue with the commented() function.

From what I see, it only supports a single argument string, not multiple parameters. I tested a few variations using the documented format like:

issue in commented("by username after 2023-01-01 before 2023-02-01")

…but in my case, they still didn’t work as expected.

So I’m wondering:
Is this functionality available only when the JQL Argon app is installed? Or should this work out-of-the-box in Jira?

Would appreciate any clarification 🙂

Bartek Szajkowski _ Orbiscend OU
Atlassian Partner
April 1, 2026

Dear @Nadir Jabbarli 

Thank you for reading my article.

To clarify a couple of things:

Yes, this functionality requires the Argon Powerful JQL Search app to be installed — it won't work out-of-the-box in standard Jira.

 

Also, the commented() function uses separate parameters, not a single string. The correct syntax is:

issue in commented("subquery", "author", "start_date", "end_date", "content")

 

So your example would look like this:

issue in commented("project = DEV", "username", "2023/01/01", "2023/02/01", "")

 

Empty strings  ""  are used as placeholders for parameters you want to skip.

 

Hope my answer help.
Greetings

Bartek 

 

Like Nadir Jabbarli likes this
Nadir Jabbarli
Contributor
April 2, 2026

Thank you for your clarification and for taking the time to explain. I actually tried the syntax you suggested. But it didn’t work in my Jira environment. I just wanted to share this in case it’s helpful for others who might run into a similar situation.

Bartek Szajkowski _ Orbiscend OU
Atlassian Partner
April 2, 2026

Hi @Nadir Jabbarli 

Thanks for your message.

Could you please send to me what exactly you want to do? Please send your query.
You can send it here, or directly to my mail -  bartek@orbiscend.com  - as you wish.
We will return to you asap (even if you write directly to mail, I also will provide answer here to keep other informed).

I look forward your feedback.

Bartek

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events