Settings and activity
20 results found
-
160 votes
An error occurred while saving the comment 
Jeff Creedon
supported this idea
·
-
67 votesJeff Creedon
supported this idea
·
-
138 votesJeff Creedon
supported this idea
·
-
127 votesJeff Creedon
supported this idea
·
-
85 votesJeff Creedon
supported this idea
·
-
20 votesJeff Creedon
supported this idea
·
-
1,607 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,755 votesJeff Creedon
supported this idea
·
-
1,026 votes
-
35 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
-
840 votes
-
268 votes
-
69 votes
-
297 votes
-
341 votes
-
179 votes
-
1,570 votes
-
864 votes
-
2,289 votes
-
1,559 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.