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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,733
Community Members
 
Community Events
177
Community Groups

Automatisation - don't work

Edited

Good morning,

I create an Automatisation task and I don't understand why it tells me "The following tickets did not match the condition"

My actions are simple:
* Field value changed: status.
** Type of change: any change.
* Update is equal to 1 minutes ago (for the test)
* State is part of pending.
* THEN : Add a comment.

It sees the change in my ticket, but does not comment.
Do you have an idea ? 

2 answers

1 accepted

3 votes
Answer accepted

Hi @Marie Laplise,

We cannot see the exact data nor your automation rule, but most likely the problem is in your "update is equal to 1 minutes ago" part.

Jira uses milliseconds for time based calculations and I would suspect that the time of change will not be exactly one minute ago. To make sure your automation works, I would remove that condition, since you are already responding to the field value changed event.

(on a side note: I also don't know what you mean by "State is part of pending" - but that is probably not the issue here)

Hope this helps! 

Hello @Walter Buggenhout _ACA IT_ ,

Thank you for your answer,
In the future, I would like to warn my users that if they do not answer the ticket will be closed.

"State is part of pending" is a condition.

Attached is a screenshot,  in French, sorry  :

image.png

Hi @Marie Laplise,

No worries about the French 😉

I believe it would be easier for your use case to use the SLA's to set up what you are trying to do. I think you are describing a classical use case where an issue enters status Pending (and thus requires an answer from the customer) and you want to close an issue automatically if you wait too long for a reply. You expect an answer within 40 hours after entering status pending, if I understand correctly.

You may create an SLA that looks like this:

Screenshot 2023-01-03 at 14.50.35.png

obviously update the conditions to match your statuses and workflows.

Then set up an automation rule that responds to this SLA like this:

Screenshot 2023-01-03 at 14.52.56.pngThis rule will send out a message 3 hours before the SLA target is reached. So in the example after 37 hours of waiting time.

Hope this helps! 

You can even use the same SLA to automatically close the ticket when the SLA target of 40 hours is reached:

Screenshot 2023-01-03 at 14.55.32.png

Thanks for the tips @Walter Buggenhout _ACA IT_ , it works.

And happy new year! :)

Thx @Marie Laplise! Glad it does and best wishes to you too! Since my tips helped, could you accept the answer below? That makes it easier to retrieve for other people with similar challenges! 🤗

Suggest an answer

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

Atlassian Community Events