nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Searching for issues by last public comment.

Onyx Gendry

Type: Cloud

Is there any way to filter issues from a search based on the last comments date and visibility status using in built field.

I can see the Comment fields in the CSV export contain a Date time stamp. However I suspect this is sourced from another field in the backend not available from the UI.

Reason for Query:

Attempting to build an automation to prompt SD Agents to follow up on aging cases.
Need to additionally be able to determine if the last comment was internal.

Current automation leverages the updated field.

Accepted answers

Muhammad Ramzan_Atlassian Certified Master_

Hi @Onyx Gendry ,

Welcome to Atlassian community. I have created the example rule for you and it will be fulfilling all of your needs.

You can use this condition and compare it with false

{{issue.comments.last.properties."sd.public.comment".internal}}

It will get all issues where last comment is a public comment.

Here is the snapshot, you can use your query as it is in the scheduled and use the remaining conditions to fulfill your needs.

Please feel free to contact back any time if you face any issues

All comments

Gökçe Gürsel {Appfire}

Hi @Onyx Gendry ,

You can use the Comment Enhancer app for this.

It has features called Last comment, Last Commenter, and Last Comment Date custom fields that will help you to stay on top of your tickets. You can also search issues against these custom fields. Just start typing custom field names, and search issues. You can also add comment custom fields to the issue navigator and see the results accordingly.

Last comment-Comment Enhancer.png

Please let me know if you have further questions.

Cheers,

Gökçe

Please note that I'm one of the members of the Snapbytes team.

Muhammad Ramzan_Atlassian Certified Master_

Hi @Onyx Gendry ,

Welcome to Atlassian community. I have created the example rule for you and it will be fulfilling all of your needs.

You can use this condition and compare it with false

{{issue.comments.last.properties."sd.public.comment".internal}}

It will get all issues where last comment is a public comment.

Here is the snapshot, you can use your query as it is in the scheduled and use the remaining conditions to fulfill your needs.

Please feel free to contact back any time if you face any issues

Onyx Gendry

Hi Gökçe,

I appreciate the suggestion, unfortunately this isn't what I'm after. I'm only looking to leverage the in-built standard fields/values as I have neither the clout nor justification for a 3rd party app, free or otherwise.

Kind regards,

Onyx

Onyx Gendry

Hi Muhammad,

Thanks for the cheery welcome and appreciate the swift response. This looks like half the puzzle, I'll have to give it a test post my extra long weekend leave and get back to you.

The properties stuff is really powerful but the learning curve is rather steep.

Kind regards,

Onyx

Muhammad Ramzan_Atlassian Certified Master_

You are always welcome, We just need to figure out how to use it so it can solve your whole puzzle

Please feel free to reply back if you face any issue.

Onyx Gendry

Hi Muhammad,

This certainly put me on the right track. After an afternoon buried in the documentation with the fresh perspective you gave me I got it to do what I was after and learned some neat basics on automation. Learning new things is always exhilarating, especially when they work properly.

While it certainly isn't the most efficient query/notification scheme, here's the final product for reference.

Schedule filters in anything with an appropriate status during work week days on a CRON schedule. (Running at midnight)

First IF: Filters out any issues who's last comment is within the last 5 days. (Might have to refine this one at a later date)

Action: Had to add an action to save it so it just logs something.

Second IF: Checks visibility on Comment (Internal) + validates created time. (Validation is probably unnecessary but I'm paranoid fool so i put it in anyway.)

Action: Sends email to Assignee with appropriate message

Second IF: Checks visibility on Comment (External) + validates created time. (Validation is probably unnecessary but I'm paranoid fool so i put it in anyway.)

Action: Sends email to Assignee with appropriate message

Kind regards,

Onyx

Thomas Rotthowe

Hi Gökce,

I would like to use the comment enhancer app - but can not find it in the market place. Can you give me more details on the supplier?

I am also trying to create a queue which shows me all tickets with their last comment date, last user commenter (who is not an agent) to make sure we do not miss the latest commented tickets with are waiting for replies...

Thanks in advance!

Thomas

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management