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; } } }

JIRA Automation: Group qualifying Last Comments by their ages

Colin_Turner_em1cll

Hi all!

Goal: send different Slack messages based on the age of qualifying "Last Comments"

Ex: I add a comment with the keyphrase "PLS_ESCALATE" to items. I want to receive different messages around the time that comment hits ages of 24h, 48h, and 72h, respectively -- if at that time it's indeed still the last comment.

My current design is to use a "scheduled" trigger running regularly, looking for items with a qualifying last comment, then bucketing them into age intervals to report differently.

I've got the first part working, but can't find a component+smartvalue pairing to do the second part. Is this a case for advanced branching? If/Else? It's hard to know, because I have no last-comment date analysis working anywhere yet -- not for "issue.last.comment.created" nor for Last Comment.created -- so I am going in circles.

Can anyone advise on how to judge the age of the last comments in JIRA Automation?

Edit: bummer: rubber-duck-debugging style, I see now that it's "comments" in the smartvalues, not "comment" 🤦‍♂️, so I may make some progress again, but any advice still appreciated

Accepted answers

Bill Sheboy

Hi @Colin_Turner

You seem to have the smart value expression's attributes out of order. Please try this to find the age of the last comment added in hours using the diff() function:

{{issue.comments.last.created.diff(now).hours}}

If that does not help, please post the following for more context:

* what type of project is this (e.g., company-managed, team-managed, JPD, etc.),
* an image of your complete automation rule in a single image,
* images of any relevant actions / conditions / branches,
* an image of the audit log details showing the rule execution, and
* explain what is not working as expected and why you believe that to be the case.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Colin_Turner

You seem to have the smart value expression's attributes out of order. Please try this to find the age of the last comment added in hours using the diff() function:

{{issue.comments.last.created.diff(now).hours}}

If that does not help, please post the following for more context:

Kind regards,
Bill

Colin_Turner_em1cll

oops

Colin_Turner_em1cll

Hi @Bill Sheboy, it's a company-managed JIRA cloud project

complete automation:

Screenshot 2025-02-05 at 10.56.51 AM.png

and the error log:

Screenshot 2025-02-05 at 10.59.14 AM.png

I'd like to report the issues whose last comment contains a given string and is between given ages in hours, but it doesn't seem to be reading the smartvalue in identifying them

Colin_Turner_em1cll

I got there!

I was surprised that pre-pending "lookupissues" to the smartvalue in the smartvalue comparison component got me over, was a wild shot

Screenshot 2025-02-05 at 11.42.26 AM.png

Bill Sheboy

When the scope is a single issue, use the {{issue.someField}} and when using Lookup Issues, it is that scope for the set of issues {{lookupIssues.someField}}

Please note well: if lookup results have multiple issues, that expression will be a list of values, not a single one. How many issues do you expect the lookup to return?

Louise Baker

@Colin_TurnerI'm curious about your Last Comment field - I'm trying to do something similar-ish. What does {{LastComment}} refer to in your latest post? Is it a smartvar, and what is it referencing?

Colin_Turner_em1cll

Hi @Louise Baker in order to kick off the advanced branch, I had to name the set, but the set was just my {{lookupIssues}}, so I played along and put that in the top field, and then {{LastComments}} in the bottom field of the branch component. I must not fully grasp their purposes, but that's what it refers to

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud