Settings and activity
10 results found
-
174 votes
Yeimy Pilco
supported this idea
·
-
1,589 votesYeimy Pilco
supported this idea
·
-
6 votesYeimy Pilco
supported this idea
·
-
32 votes
Hi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
Yeimy Pilco
supported this idea
·
-
41 votesYeimy Pilco
supported this idea
·
-
52 votesYeimy Pilco
supported this idea
·
-
1,913 votes
Hi,
Thank you for your valuable suggestion. While we won't be implementing this idea in the immediate future, it has been added to our list for future consideration.
We continuously review user feedback to inform our development priorities, so your idea remains on our radar.
Best regards,
The Atera Team
Yeimy Pilco
supported this idea
·
-
66 votesYeimy Pilco
supported this idea
·
-
1 vote
An error occurred while saving the comment Yeimy Pilco
shared this idea
·
-
211 votesYeimy Pilco
supported this idea
·
Time-based ticket automation rules still require a trigger (for technicians to change the status of these tickets. That defeats the purpose of calling this an automation. EVEN if we had to manually change the "Activity Status" to "Awaiting Requestor reply" is better than setting the ticket as "Pending" under Pending status. In order for this automation to trigger, it needs a trigger and we cannot manage to use the Status and set it to pending. We rather use the activity status. Please note this has nothing to do with the time based (as we are familiar with this). We are more concerned with the trigger of this automation.