Forums

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

Notification for issue sitting in progress for X days with no comment (Next Gen)

Josh Allen
Contributor
September 4, 2020

I'd like to be notified when an issue has been sitting in a specific status (in progress) AND has NOT been commented.

I'm trying to identify issues that haven't really be updated, so I'm willing to use the Log Work instead of commented OR the Updated status. 

I've tried using Jira Automation:

  • Trigger: Issue Transition
    • from To Do TO In Progress
  • If: all match
    • {{comment}} equals EMPTY
    • updated <-5m (I used minutes for testing purposes. I'd probably use something like 24hours)
  • Then: Send email

I was able to get notified, but it notifies me the second it transitions. I'm essentially trying to get it to notify me if it hasn't been updated at 5 minutes (or in the past 24 hours)

3 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 4, 2020

Hi @Josh Allen 

Instead of using the transition trigger, you could use the schedule trigger, and check every X minutes (or hours, or whatever).  Add a condition after the trigger to confirm that the issue is in progress (or use JQL in the trigger to be more efficient).  Maybe something like:

  • Trigger: scheduled every 24 hours, where JQL is status = "In Progress" AND updated < -5m
  • Condition: comment is EMPTY
  • Action: send email

 

Best regards,

Bill

Josh Allen
Contributor
September 4, 2020

YES! Thank you very much @Bill Sheboy 

This is the easiest approach for me and that worked perfectly.

Like Bill Sheboy likes this
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 4, 2020

By the way... this method *could* return multiple issues satisfying the trigger and JQL, so you have a couple of choices:

a) Use a branch to iterate over the issues, sending an email for each.  Given your problem description, this seems like the best approach to confirm that the comment is empty by putting it inside the branch.

  • Trigger: scheduled and JQL
  • Branch on the JQL
    • Condition to check comment
    • Action to send email

2) Us a lookup issues action with the JQL to consolidate the list into one email.  This could have "false positives" as you may not be able to detect the empty comment in the JQL.

 

__Bill

Gizem
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!
April 21, 2022

@Bill Sheboy Could you please help me to configure your second option to send a daily list of "not prioritized" items in one email?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 21, 2022

Hi @Gizem -- Welcome to the Atlassian Community!

First thing: please consider creating a new question and linking to existing threads.  That will ensure the most number of people see your question to offer ideas.  Otherwise only the people following existing threads will see them.  Thanks!

Regarding what you asked...

Are you using Jira Cloud or Jira Server/Data Center, as Lookup Issues is only supported with Jira Cloud.  Let's assume that is what you have.

Without knowing the specifics of what you mean by "not prioritized", I am going to assume you have added a value to Priority for "not prioritized".

  • trigger: scheduled with no JQL
  • action: lookup issues using JQL.  Here is some example JQL which you can update to match your project name and needs.
    • project = myProjectName AND statusCategory != Done AND priority = "Not Prioritized"
  • advanced compare condition: test if there are issues to send in the email
    • first value: {{lookupIssues.size|}}
    • condition: greater than
    • second value: 0
  • action: send email, with something like this in the email body
Here is the list of issues:
{{#lookupIssues}}
* {{key}} {{summary}}
{{/}}

 

Please note you can also do this with a saved issue filter and a subscription, rather than an automation rule.

 

Kind regards,
Bill

1 vote
Gökçe Gürsel {Appfire}
Atlassian Partner
September 4, 2020

Hi @Josh Allen ,

You can also use an SLA to be notified since it captured the necessary conditions better than Automation and you don't need to spend your free Automation executions for this. 

You can use Time to SLA to get notified via Slack as well as email.

Check this configuration out:

SLa start.pngYou can set your SLA Goal as you wish and add a notifier at the 24hour mark. (SLA Goal is 24 hours in this example)

notifier.pngYou can combine other features of Time to SLA such as detailed reports, global notifier, and recurring notifications with this configuration to easily manage your idle tasks.

Let me know if you have any questions. 

Cheers,

Gökçe

Josh Allen
Contributor
September 4, 2020

Thank you @Gökçe Gürsel {Appfire} 

This looks interesting. Was wondering how to do SLAs outside of Service Desk. Not quite needed yet on our team I think, but will consider for the future.

Gökçe Gürsel {Appfire}
Atlassian Partner
September 4, 2020

Thank you for the update. :) Please don't hesitate to reach out if you need any assistance in the future. 

0 votes
D Wilson
Community Champion
September 4, 2020

@Josh Allen 

 

Another approach would be to use saved filters and subscriptions.

1. Define the filter you need to show the tasks to be reported on

Screen Shot 2020-09-04 at 8.59.50 AM.png

2. Save It

 

Screen Shot 2020-09-04 at 9.00.04 AM.png

 

3. Browse to the list of filters "Filters --> View All filters" and locate your saved filter

4. Click on the eclipse menu and select manage subscriptions --> add subscription button on the next screen

Screen Shot 2020-09-04 at 9.00.59 AM.png

5. Set the recipients, frequency, and time you would like to be notified each day.

 

Screen Shot 2020-09-04 at 9.01.06 AM.png

 

6. Click Subscribe.

This also allows for others to subscribe to the same filter on a frequency they chose.
You can update the saved filter if your need change later
This doesn't take automation cycles if the number available is a concern for you.

Josh Allen
Contributor
September 4, 2020

Thanks @D Wilson 

I think this is also a good approach and appreciate the advice.

Like D Wilson likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events