- or
No existing idea results
- ~ No ideas found ~
5058 results found
-
Deferring Tickets for Later
I appreciate the ability to schedule tickets when a tech creates them, but i'm also looking for the ability to defer tickets that come into the helpdesk by users if work is to be completed at a later date.
Example: A manager opens a ticket to have a staff member offboarded, or there's a change of staff a couple of weeks down the road. Currently we have to delete the ticket and create a new scheduled ticket manually, whereas this would be a lot easier if we can defer the ticket to a later date and remove it from view until that date comes around. This also prevents it from messing with metrics.
Thanks,
JeremyI appreciate the ability to schedule tickets when a tech creates them, but i'm also looking for the ability to defer tickets that come into the helpdesk by users if work is to be completed at a later date.
Example: A manager opens a ticket to have a staff member offboarded, or there's a change of staff a couple of weeks down the road. Currently we have to delete the ticket and create a new scheduled ticket manually, whereas this would be a lot easier if we can defer the ticket to a later date and remove it from view…
2 votes -
stop emails automatically sending
Ability to send emails to third parties or different users without having to create a separate ticket or include the original requester in the email thread. It is not practical to change the requester every time we need to communicate with someone other than the person who logged the ticket.
Additionally, it would be beneficial to have the option to choose whether outbound emails include the entire email chain. Currently, we often have to temporarily change the requester to obtain approval and then revert it back, but this results in the entire email chain between the approver and us being included in any future communication with the requestor, which is not ideal.
Furthermore, I would prefer if responses to a ticket are not automatically forwarded to the requester. While there should be an option to do so, it should not happen automatically as most of the time the requester does not need to see the responses.
Ability to send emails to third parties or different users without having to create a separate ticket or include the original requester in the email thread. It is not practical to change the requester every time we need to communicate with someone other than the person who logged the ticket.
Additionally, it would be beneficial to have the option to choose whether outbound emails include the entire email chain. Currently, we often have to temporarily change the requester to obtain approval and then revert it back, but this results in the entire email chain between the approver and us being…
2 votes -
Multiple Default Contracts
I think contracts should be re-worked so that you can set multiple default contracts throughout all clients (which appear by default across all clients, including newly created ones). Then within each client you can select one contract as a primary contract, which will be the one assigned to new tickets.
I also think the contracts should not have the same name - or be auto generated based on the client name and the attached products etc.
This method will allow
3 votes -
Scripts to prompt for input
Have scripts to prompt for input. for example, if I wanted to create a new local user and add to the administrators group. I would run a script but have it prompt for the username and/or password.
I have a script created and I can either have a set password for all my clients, BAD, or edit the script for each client I would like it ran on, not ideal.
1 vote -
Warranty Status on Devices
The ability to see warranty information on devices.
107 votes -
Tab order fix for Product Family
I noticed the tab order for the child objects under Product Family requires you to tab past the Product Family to select a child object. This is very confusing for someone who uses a screen reader to navigate.
1 vote -
Custom Ticket Types
It would be very helpful to have custom ticket Types. This would allow for creating different kinds of tickets and, importantly, applying different ticket automation rules.
Example... "normal" type tickets (problem, incident, etc) can generate emails sent to customers. But a custom Type (Sales) can be configured to NOT generate a notification email, and auto-set Status to a fitting custom status (Sales - Requested, Sales - Ordered, etc).
Currently, I am doing the same thing by using custom Product Family options, but those fields are not available in the mobile app, which we do use regularly.
13 votes -
Customer IT Team Access
Customers IT Team having access into atera as that client only. Limited access with limited use and at a cheaper cost to compensate for not having access to the full range of features.
5 votes -
Password protect the Atera agent from end-user uninstalls
Password protect Atera Agent from being uninstalled. I have had several users uninstall the agent from their systems. Most do not recognize the software and remove it. Others are just nosy. And others see the new software added and remove it because they don't like control, "Big Brother" .
I would like the option to place a check mark to turn on Password protection.
1,611 votesCongratulations 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!
-
Agent page - Show Reboot Required
Would be great to see if the device is in need of a reboot on the agent page, to the right of "Online"
I mocked up a pic but I guess I cannot attach images..
4 votes -
make email not a required field for a contact
Make email not a required field for contact. We are having to enter arbitrary email addresses to create contacts that do not provide email address (or do not have one). This results in false data in our customer/contact information.
4 votes -
Rename Devices from Customer/Devices Screens
Would make renaming devices a much easier process if it could be done from the Customer Devices tab, or Devices page. Having to go into each individual agent, hit edit, then hit agent, then go back to the customer devices page is a lot of clicks and window loads when you're going through and renaming a bunch of agents. A way to do this without needing to actually go into each individual agent would make this a much more streamlined and significantly faster process!
2 votes -
Automatically send an email when computer is added to account by agent installation
Automatically send an email when a computer is added to account by agent installation. Ideally, the default behavior would be configurable by the admin for all customers, but each customer could override the default behavior and even choose which email(s) to send the email to.
This will trigger in-house procedures to finish onboarding new customers once they are in Atera.
4 votes -
branding color
Add the ability to change our branding color under "Admin > White Label > Logo and Color" back. At some point, it was removed and support said I should create a feature request to add it back.
7 votes -
Dashboard - Compliance/Health Widgets
The Dashboard should have widgets for a compliance overview. Clients missing critical & security updates. Clients missing Anti-Virus software, or disabled/stopped, behind AV updates. Windows Firewall status active/disabled.
7 votes -
reminder
It would be nice to be able to add a reminder for non-important issues whenever I remote into a end user's system. There might be low priority items like "purge folder X after x/xx/xxxx." or "Reminder: This user has a static IP set."
As of now I'm using the notes, but it would be nice if I was somehow able to be reminded when I'm logging in so I can address outstanding non-urgent issues.
2 votes -
Helpdesk Tickets with out user having to log in
Ability to let tickets to be created by unauthenticated users. Not having to create a contact to create a ticket.
1 vote -
Improving code reusability and batch flow control on scripts
In order to avoid code duplication between scripts and improve reusability and flow control on business-logic, it would be very interesting to have the possibility to make calls between scripts to other existing scripts. I mean, for instance, make calls on a powershell script to another existing powershell scripts:
switch(some-needed-conditional){
"if - A": [Call-to]::Atera-script-1
"if - B": [Call-to]::Atera-script-2
"if - C": [Call-to]::Atera-script-3}
2 votes -
Better automation for tickets
More trigger options for ticket automation and the ability to set ticket field values based on keywords etc.
13 votes -
Remove required fields for technician
When creating a ticket as a technician, be able to override the required fields so that they are not required.
4 votes
- Don't see your idea?