- or
No existing idea results
- ~ No ideas found ~
4830 results found
-
Ability to copy a ticket
Sometimes I have to create several tickets that have all the same information - it would be helpful if we could "copy" a ticket as a starting point and have it bring over all the info (categories etc.)
2 votes -
Use multiple monitors at the same time with AnyDesk.
Use multiple monitors at the same time with AnyDesk.
3 votes -
Print MULTIPLE Tickets
I would like Atera to have the ability of print multiple tickets.
In the past, I see that someone suggested the Idea and It got moved to production and it's live now.
However...
In my organization, we are ask in a monthly base, to describe and summarize our 'highlights'.
What I have been doing it, it's I go through 20~ tickets manually, select the print option, and save it as a PDF...
Then I use AI to give it formatting base on the ticket in that PDF.
I would like, and I think it will be useful-- to allow multiple tickets to be selected, so you can 'print' all of that selection, so it generates a PDF containing all those tickets merged into a single PDF, instead of various documents.
I would like Atera to have the ability of print multiple tickets.
In the past, I see that someone suggested the Idea and It got moved to production and it's live now.
However...
In my organization, we are ask in a monthly base, to describe and summarize our 'highlights'.
What I have been doing it, it's I go through 20~ tickets manually, select the print option, and save it as a PDF...
Then I use AI to give it formatting base on the ticket in that PDF.
I would like, and I think it will be useful-- to allow multiple…
2 votes -
miradore
Miradore integration
3 votes -
Emails to other than the requester
I would like to be able to start a "side conversation" on a ticket for when I need to communicate with a third party related to the issue at hand.
70 votes -
Ability to filter the run of IT automation and threshold profiles by agent details
If we create an IT automation or threshold profile that's only for Windows Servers then we have to create Profile at each and customer assign every Server to it and then assign every of that Server profiles to the automation profile
That's cumbersome and prone to errors
Much more efficient would be a set of filters at the automation profile, like "is Server" or "is a domain controller" or maony other smart things.
We would just assign am automation oder threshold profile to customers and it runs only at the matching agents
2 votes -
Include snippet for Contact First Comment
Crate a snippet for Contact First Comment so that it can be added to an email template used for resolution.
3 votes -
Need to be able to tie assets to a user
At this time we are using Atera for several things it was not initially designed for. We are using it as an asset management solution as well as the main development and design for what Atera is made for. We are able to add assets and assign them to a user however when we search the user nothing in your current set up lets us see all the assets we have associated to that user.
13 votesHi,
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
-
Kill Splashtop SOS sessions
Terminate Splashtop SOS sessions directly from Atera when the session limit message appears, instead of waiting one hour for them to expire automatically
2 votes -
Ticket tabs "more"
When there are more than (on my screen) 13 ticket tabs open, you get a "x more" (x being a number) stack to the right.
I cannot find an option to close open tabs in that list.
Please add an "x"-Button next to ticket title in that list.2 votes -
Make all custom fields available in scripts
Currently only agent custom fields are available to use in scripts. All custom field should be available (where sensible). For example, customer wide custom field containing data we want to access in a script.
5 votes -
Webhooks
Webhooks triggers on Alerts
We are exploring the possibilities of using Webhooks to integrate Atera with Freshservice for the Alert system.
Currently, your Webhooks system only allows actions to be triggered against tickets, meaning within ticket automations. We have already confirmed with your support team that a ticket created by an alert does not automatically close when the alert is resolved, which leaves the Freshservice alert disconnected if it is resolved from Atera, making the integration less functional.
We have found that in Zapier, you do have triggers available for both alert creation and resolution. Therefore, we understand that the system should be capable of doing the following:
We would like to be able to trigger Webhook calls on alert creation and resolution events. We do not want to use Zapier as Freshservice has a listener element where the Atera hook can be launched, and using Zapier would unnecessarily increase steps and operational costs.
This functionality (attaching Webhook calls to alert creation and resolution events) would be the cleanest and most effective way to keep alerts connected between the two systems and ensure we don’t miss anything.
Webhooks triggers on Alerts
We are exploring the possibilities of using Webhooks to integrate Atera with Freshservice for the Alert system.
Currently, your Webhooks system only allows actions to be triggered against tickets, meaning within ticket automations. We have already confirmed with your support team that a ticket created by an alert does not automatically close when the alert is resolved, which leaves the Freshservice alert disconnected if it is resolved from Atera, making the integration less functional.
We have found that in Zapier, you do have triggers available for both alert creation and resolution. Therefore, we understand that the…
12 votesHi,
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
-
Device Info History - Hostname, Logins, Reboots
There are many ideas like this one, but they are limited to very specific things - most of them targeting the user history.
We need more than just user history, we need ALL history. Most things on the Overview page should have their own history tracking. Sure, things might be tracked in the activity log - but sometimes we need very specific information that may not be logged at all.
First and foremost, every one of these fields should have a little icon next to them to display the history of the field. You will also note I have included an additional field, called 'Device hostname', because the simple fact is you can change the name of a device in Atera completely different than the hostname of the device... but both are important, and thus should not be ambiguous.
Device name
Device hostname
Domain
Public IP
Last login
Last rebootFurthermore, it would be good to see the history for the owner info:
Customer
Folder
ContactAnytime a new field is added here, it should also be considered for history tracking. Perhaps there should be a limit on things like 'Public IP' and 'Last reboot' history, but that can easily be an internal setting in the admin console or set to a number that nobody would have a problem with, like 30.
There are many ideas like this one, but they are limited to very specific things - most of them targeting the user history.
We need more than just user history, we need ALL history. Most things on the Overview page should have their own history tracking. Sure, things might be tracked in the activity log - but sometimes we need very specific information that may not be logged at all.
First and foremost, every one of these fields should have a little icon next to them to display the history of the field. You will also note I have included…
6 votes -
Restrict the ability to set Closed Status on Tickets
Since "Closed" status permanently closes a ticket without giving the requester the ability to re-open it, I'd like the ability to remove the "Closed" status from the Status dropdown box.
The workflow we want to have is a technician sets a ticket to "Resolved" and then an Atera rule automatically changes Resolved tickets to Closed after a period of time which can be done. However technicians are accidentally setting tickets to "Closed" and duplicate tickets are being created when a requestor immediately replies.
I know there's an option to allow "Closed" tickets to be re-opened, however I do not want to enable that option. So we can better track repeat issues, requesters not responding and putting in more tickets later/using more of IT's time, etc.
The Data Management > Custom Fields page does not allow you to change anything about the built-in status values.
Since "Closed" status permanently closes a ticket without giving the requester the ability to re-open it, I'd like the ability to remove the "Closed" status from the Status dropdown box.
The workflow we want to have is a technician sets a ticket to "Resolved" and then an Atera rule automatically changes Resolved tickets to Closed after a period of time which can be done. However technicians are accidentally setting tickets to "Closed" and duplicate tickets are being created when a requestor immediately replies.
I know there's an option to allow "Closed" tickets to be re-opened, however I do not want…
1 vote -
Centralized Report Scheduling
A centralized way to schedule reports to their receivers so they aren't tied to specific technician as that solution is not manageable in the long run. Managing customer facing reports shouldn't be tied to a single technician and automation/scheduling on reports would be beneficial to be open to all technicians or tied to a role.
2 votes -
Device Search
We name our devices in Atera based on Site and User. However, the devices themselves are named by their asset tag. When I search in Atera under Devices in EITHER category by device name it does not find it and the name is clearly in the information Atera gathers about the device. This is frustrating - please fix.
1 vote -
"Update all" button on Devices page
I believe there should be a button within the navbar of the Devices tab that once selecting specific machines, allows you to update all patches on those machines, rather than doing a report, manually clicking all unnecessary machines or doing it patch by patch on the Patch Management page.
56 votesHi,
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
-
OTP
OTP should NOT be required for paid accounts.
OTP for trial accounts is understandable to prevent abuse, but requiring OTP for interactive installs for paid accounts is not a good idea and can severely inhibit normal, legitimate deployment of the agent.
Please consider limiting this requirement to trial accounts only.
2 votes -
Automatically close Alert tickets when resolved
Would be really helpful to have alert tickets automatically close when the alert is resolved
For example Machine status unknown ticket closes when machine is back online!218 votes -
Automatically update the Mac agents to the latest version.
Automatically update the Mac agents to the latest version.
2 votes
- Don't see your idea?