Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Task time reminder for hours, not date

Edited
Michał Piłacik
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!
Oct 10, 2023

Hi

I've seen many automation topics related to my problem, but I haven't found a solution there, so maybe I'll give you my specific case.

I want to set up notifications for our helpdesk so that the assigned person receives an email a day, 12 hours and 3 hours before the deadline. The duedate option will not work because there is no specific time, so I added a timestamp for tickets. I created various limiting rules, but in each case I received e-mails for each case (e.g. 3 hours before the time I also received them for earlier ones). It may be simple, but I think I'm too confused in it.

On the screenshot, the original rule (separate for each time), without other IF rulesBez tytułu.png

1 answer

1 accepted

1 vote
Answer accepted
Rudy Holtkamp
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 10, 2023

Hi @Michał Piłacik ,

Welcome to the Community!

Here is how you can do it in a few steps. Note that my date/time field is called End Date [Gantt]. You need to replace that with the name of your field.

  1. Trigger: Scheduled every 30,
    Use a JQL with: "End Date [Gantt]" > 0m and "End Date [Gantt]" < 25h 
    And make sure the checkbox 'Only include issues that have changed...' is not checked.
    This will prevent that you have too many issues
  2. Add an If else condition
  3. Add an advanced compare condition (all conditions match):
    First value: {{issue.End Date [Gantt]}}
    Greater than
    Second value: {{now}}
  4. Add another advanced compare condition:
    First value: {{issue.End Date [Gantt]}}
    Greater than
    Second value: {{now.plusHours(3)}}
  5. Add an action, e.g. email the assignee
  6. Copy the if-block and
    Change the second value of the first condition to: {{now.plusHours(3)}}
    Change the second value of the second condition to: {{now.plusHours(12)}}
  7. Add an action, e.g. email the assignee
  8. Copy the else-block and
    Change the second value of the first condition to: {{now.plusHours(12)}}
    Change the second value of the second condition to: {{now.plusHours(24)}}
  9. Add an action, e.g. email the assignee

The first condtion block will look like this:

image.png

 

Good luck

Michał Piłacik
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!
Oct 10, 2023

Works! I didn't know I could use issue.XXX like that..
There's still a bit of learning ahead of me ;)
In point 6 and 8 instead of greater it should be less and then it works perfectly :)
Thank you very much!

Like Rudy Holtkamp likes this

Suggest an answer

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

Atlassian Community Events