The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Activity History date fields not found in available columns from search filter

Maynard Bester
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 12, 2023

I require to add a column to my Search reflecting the 1st date (which is different from the issue being created) that an Activity Comment was made. Please help.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Hannes Obweger - JXL for Jira
Atlassian Partner
December 12, 2023

Hi @Maynard Bester

welcome to the community!

I don't think that this is available as a field/column in Jira's issue search. The only native/built-in solution that I can think of is to use Jira Automation to detect comments, and store the date of the first comment into a custom field. This custom field can then be added to your filter.

Alternatively, if you're open to solutions from the Atlassian Marketplace, you may want to check out the app that my team and I are working on, JXL for Jira

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart columns that aren’t natively available, including the date of the first comment. This is how it looks in action:

date-of-first-comment.gif

As you can see above, you can easily sort and filter by the date of the first comment, and also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

This all just works, so there's no scripting or automation whatsoever required.

Any questions just let me know,

Best,

Hannes