Settings and activity
20 results found
-
163 votes
An error occurred while saving the comment 
Jeff Creedon
supported this idea
·
-
68 votesJeff Creedon
supported this idea
·
-
138 votesJeff Creedon
supported this idea
·
-
130 votesJeff Creedon
supported this idea
·
-
85 votesJeff Creedon
supported this idea
·
-
802 votesJeff Creedon
supported this idea
·
-
1,618 votes
Congratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
Jeff Creedon
supported this idea
·
-
1,904 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
Jeff Creedon
supported this idea
·
-
1,035 votes
-
36 votes
An error occurred while saving the comment Jeff Creedon
commented
Different SLAs for Request, Change, Incident and Problem We use requests and changes to be something that could be a development (or feature request like this!) and the SLA that is tied to just priority and impact is not sufficient. Even critical development requests can take weeks to roll out, and we are getting hammered by it being tied to a 4 hour Incident SLA. Thanks
-
848 votes
-
272 votes
-
69 votes
-
298 votes
-
342 votes
-
179 votes
-
1,587 votes
-
871 votes
-
2,305 votes
Hi,
Thank you for your valuable suggestion. We recognize this is an important request in IT, however 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
-
1,565 votes
If there was a Change Management function in Atera where change plans (back out plans), scheduling and approvals could be made and then kept on a calendar, then any issues that arise could be tied to the change and techs can see what the change was and respond appropriately. It would also be nice to be able to have template notifications to contacts in the effected customer for communication.