Forums

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

How do I get trigger if worklogged is higher than a certain value?

Joana Rocha
Contributor
February 1, 2023

Hi, 

 

I'm trying to receive an email every time the work logged reaches a certain amount of time, let's say 3h or 10800 Seconds. 

 

I've tried automating this both by: 

- using a JQL

{{worklog.timeSpentSeconds}} >= 10800, and  {{issue.timetracking.timespent}} >= 10800

- advanced compare condition 

{{worklog.timeSpentSeconds}} is greater than 10800, and {{issue.timetracking.timespent}} is greater than 10800

 

With advanced compare condition I receive an email every time work is logged, even if it lower than the value defined, and with JQL I dont receive an email at all. 

 

Can someone please help me?

 

PS: the app we are using to log time is Tempo

 

 

1 answer

1 accepted

2 votes
Answer accepted
Martin Bayer [MoroSystems, s.r.o.]
Community Champion
February 1, 2023

Hi @Joana Rocha following configuratino works for me, can you check? :)

Screenshot 2023-02-01 at 11.16.28.png

Joana Rocha
Contributor
February 1, 2023

Hi! Thanks for your answer. In the meantime it is working with

{{worklog.timeSpentSeconds}} is greater than 10800 - still doesnt trigget exactly at 3h, but at least it doesnt trigger in 1 min. 

Martin Bayer [MoroSystems, s.r.o.]
Community Champion
February 1, 2023

Hi, yeah, there is no "equal or greater than" condition so I guess you can use 10799 and it will work because the lowest possible work log is 1minute

Joana Rocha
Contributor
February 1, 2023

What I mean is that I still get a trigger when something is logged with less than 10800. I get a trigger at 5 min. I'm not sure why. 

Martin Bayer [MoroSystems, s.r.o.]
Community Champion
February 1, 2023

Can you share the screenshot with your configuration?

Joana Rocha
Contributor
February 1, 2023

Sure! I changed to the variable you used, and it seems to work fine now! I think the issue was the smart value I picked didnt calculate well, but didnt give errors either. 

 

Thank you for your help!

 

Screenshot 2023-02-01 at 16.23.32.png

Martin Bayer [MoroSystems, s.r.o.]
Community Champion
February 1, 2023

Sorry, I didn't notice you use wrong variable.

  • {{worklog.timeSpentSeconds}} gives you the number of seconds of the worklog which initiated the event
  • {{issue.timetracking.timespentSeconds}} gives you the total amount of seconds logged to the issue including your new worklog

Suggest an answer

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

Atlassian Community Events