Time in Status Trigger | Voters

Time in Status Trigger

Asher Thompson

I'd like to have an automation that is triggered by the time in a status. For example: When task has been in Review status for 5 days, add tag.

Another example for user support: When task is In Progress status for 10 days, send email template.

November 6, 2023

Yanglyn Ou

I like the idea of if status is X and time in status is X hours/days then trigger X. So basically:

If Status is Stuck (for example) and Time in Status is 4 Days -> Then Add A Comment

Thilo Klingebiel

#1 is what we need

Lou Reed

No. one is what we're after. Number two is also useful, but only a bit LOL

Denia Hernández

#1 is top what we need, #2 would just be ok thanks.

Zach

Question for this group...
I think there are two asks here:
New trigger - Time in Status is...
New Condition - Time in Status is...
If we were able to release #2 (New Condition) faster, would you find that valuable or not? We think there's a quicker path to get something out here but I also realize there's probably more utility with having the trigger shipped. Maybe I'm wrong though.
(Rough example image)
Let me know!

Alex Rizea

Zach #1 would definitely be more desirable, but if #2 can be done faster that would still be great, as we can work around with a scheduled trigger (every day) to get to a similar result.

Jonathan Lefebvre

Zach #1 would be best. #2 is a great addition.

Natcho Angelo

Zach Voting Team #1

Vlad Nedelcu

Zach for my use case, #1 is crucial

Joseph Thomas

Zach the #1 would be best , but if #2 can be released faster then that would be good too.

Sam

Zach #2 would be valuable, but #1 would still be needed for sure.

Peter Krzyzek

Zach Agreed with the group: #1 ideal, but having the second idea sooner would be great and let us do more then enough workarounds to make it work.

Reuben Helmuth

Zach, I agree that both are needed, but if #2 can come faster by itself, I’m great with that as long as #1 doesn’t get totally sidelined.

Alain Hervás

#1 would be best. #2 if #1 is not forgotten forever

Gina Hanks

Zach #1 is the most crucial for our use case.

Karoline Kautz

Zach For us #2 (new condition) would be most important. Particularly if we can freely set a number of days.

Shawn Clement

Zach #1 is great and 2 is a great addition

Megan Justice

Zach #2 would be amazing. It's a great addition and I would make use of it (only do a thing if time in status is less then or greater than X).

#1 would be more useful. But #2 is highly supportive.

Lauren Stead

Zach voting for #1, but we could theoretically work with #2.

edit: wanted to chime in to agree with above comments that if #2 is implemented for dev speed, please do not forget/sideline #1!

Kylen Downs

Zach Similar to other responses here. #1 would be ideal but #2 would work, albeit a little more effort to implement effectively in our use case.

Marcelo Tavares

Zach #1 is what we need #2 is a great addition.

Marge

Zach No. 2 would be great for us already! THANK YOU SO MUCH!!!

Eric Carson

Zach I vote for both. It's mutually supportive.

Susan Sloan

Alain Hervás yes, this exactly :)

Crystal Dunn

Zach, echoing the majority - 2 would be great and will help alleviate the problem we are looking to solve but there will be use cases where 1 will be preferred.

Shahen Halebian

Zach #1 would be better, but do number 2 first if you can get it done faster. For number one, there is a work around, but you have to create a custom field for each status. Create a date custom field, trigger the date when the status is set or changes to a certain status. Then, use the automation "# of days/weeks/months/hours after/before the custom field date". This is basically #1, so if you can just have it as an automation option instead of needing to create a bunch of custom fields, that would be great!

Carlos Leon

Zach faster the better

Miles

Zach #1 my lord!

Liesl Ludeke

Zach yes to #2

Kristina Graham

Zach I vote for both! Open for either option if they can't be released together, but both would be such game changers. Thanks for asking!

Reuben Andrews

Zach #1

Rebecca Julius

Zach #1 is the only one that would be useful for me here, but I appreciate that you're working towards it either way.

Zach

Hey thanks everyone!

I think we'll continue forward with releasing #2 as we can get that done sooner. Trying to get wins where we can while still focussing on our larger initiatives for Automations! Working on it now.

Yanglyn Ou

Zach This doesn't make quite as much sense to me because when a task is created, it will by default have been in a whatever status you choose for 0 days. I added a comment before seeing this saying:
"I like the idea of if status is X and time in status is X hours/days then trigger X. So basically:
If Status is Stuck (for example) and Time in Status is 4 Days -> Then Add A Comment"

Kristina Graham

This is an important feature that my team is in desperate need of. It would be great to specifically tag an assignee if a task has been in a certain status for a certain amount of days, and the tag would act as a reminder.

Susan Sloan

I would like to add my voice to this request, it's a real pain-point for me in managing support tasks.

Sam Grant

Any Updates Luci N.? Do you know where/when this is in the timeline, as it seems like a few people are asking for the feature 😁

Shahen Halebian

This is hugely needed. There are so many uses cases for having this as a trigger, and as I understand how automations are built, this doesn't seem too complicated to create.

Philippe GUERIN

I hope too

→