- or
No existing idea results
- ~ No ideas found ~
4765 results found
-
Ticket Timer Automation rule
Please allow me to trigger with Automation rules the ticket timer, the automatically start timer on ticket open is not an accurate way to track time. My Goal is to set automation flows that automatically start and pause the timer based upon my ticket status.
11 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. You are also welcome to review the most recent comment added from our Product Marketing Team.
http://atera.uservoice.com/forums/936306/suggestions/50683820
Best regards,
The Atera Team
-
Patch & Automation Feedback Too Vague
This has to be the single most painful feature for us. The report may as well not exist because it doesn't tell us anything meaningful about 90% of the time, and it is incapable of reporting current progress.
It also lacks any detail around each sub-process start/finish time, as well as the overall finish time of the entire process.
We need something that can provide us with a granular status where each item in a bundle is reported as being started, show any in-progress status that is provided by the installation package, and provide a finish timestamp for each item along the way.
This arbitrary message of "Unable to fetch information from agents." is absolutely ridiculous... why did it fail to fetch? How far did it get in the process? What happened in the process? Is the agent responsive?
MORE DETAILS!!!!!!
This has to be the single most painful feature for us. The report may as well not exist because it doesn't tell us anything meaningful about 90% of the time, and it is incapable of reporting current progress.
It also lacks any detail around each sub-process start/finish time, as well as the overall finish time of the entire process.
We need something that can provide us with a granular status where each item in a bundle is reported as being started, show any in-progress status that is provided by the installation package, and provide a finish timestamp for each item…
4 votes -
Ability to delete within tickets PLEASE!
Users often send things to their tickets that are completely unrelated. The tickets get messy. We need a way to delete information that is sent to tickets please!!!!!!!!!
4 votes -
Improve adding Manual Time Entries
In the new UI, entering manual time entries is very laborious.
Having to enter HH:MM:SS and then type AM or PM, twice (start and finish) multiple times per day is very annoying.
It should be in 24-hour format. So we just enter, for example, 11.48 and 13.17, and that’s it. If we don’t enter seconds then these should default to 00 on seconds.
227 votes -
Expand Asset Warranty Support to Additional Vendorsv
Hi Team,
Currently, automatic warranty syncing is only available for Dell and Lenovo devices. While this is a great feature, many environments (including ours) consist of a mix of vendors such as HP, Microsoft Surface, Apple (Mac), ASUS, and Acer.
It would be highly beneficial if Atera could expand automatic warranty syncing support to include these additional manufacturers. This would help streamline asset management, reduce manual data entry, and improve accuracy when tracking warranty status across all devices.
Even partial support or API-based integration for these vendors would be a valuable enhancement.
Thank you for considering this request, and we look forward to any future updates in this area.
Hi Team,
Currently, automatic warranty syncing is only available for Dell and Lenovo devices. While this is a great feature, many environments (including ours) consist of a mix of vendors such as HP, Microsoft Surface, Apple (Mac), ASUS, and Acer.
It would be highly beneficial if Atera could expand automatic warranty syncing support to include these additional manufacturers. This would help streamline asset management, reduce manual data entry, and improve accuracy when tracking warranty status across all devices.
Even partial support or API-based integration for these vendors would be a valuable enhancement.
Thank you for considering this request, and we…
2 votes -
Ability to Edit
Often we receive out of office replies, large signatures, or extraneous information (like a giant forwarded email string) in tickets. Sometimes, because of how Atera is designed, we put the wrong info in a ticket. We have to have the ability to clean this up. Even if it's an option we can click in Admin we need that option.
It's at the point where I'm ready to look for another helpdesk application.
2 votes -
EDIT TICKETS
Please allow us to edit tickets!!!!! There's no way to fix errors - you have to add it all again - I'm really frustrated with this software and we haven't had it six months. Looking at other options.
2 votes -
Agent version update options
There's an Agent Version listed on the Overview tab of each device; if there's an updated version available, it should be flagged or otherwise highlighted.
For each customer's device listing, I should be able to have a column listing the installed Atera agent version. If there's an updated version available, it should be flagged or otherwise highlighted.
If there's an updated Atera agent available, for every device that already has an agent, I should be able to generate a push install for each of those devices, preferably by customer.
For each remote access tool--whether Splashtop, Anydesk, Teamviewer or ScreenConnect--I should be able to see the same information regarding updated versions, and push updates to devices needing updated versions.
There's an Agent Version listed on the Overview tab of each device; if there's an updated version available, it should be flagged or otherwise highlighted.
For each customer's device listing, I should be able to have a column listing the installed Atera agent version. If there's an updated version available, it should be flagged or otherwise highlighted.
If there's an updated Atera agent available, for every device that already has an agent, I should be able to generate a push install for each of those devices, preferably by customer.
For each remote access tool--whether Splashtop, Anydesk, Teamviewer or ScreenConnect--I should…
2 votes -
Status Selection on Ticket Creation (Dashboard)
Feature Request
Add a Status dropdown field to the ticket creation form in the Atera RMM dashboard, allowing the technician to set an initial status at the time of ticket creation rather than defaulting all new tickets to "Open."Current Behavior
All tickets created from the dashboard default to "Open" regardless of context. There is no way to set the status during creation — it must be changed as a second step after the ticket is saved.Requested Behavior
When creating a ticket from the dashboard, the technician should be able to select a status from a dropdown at creation time.Feature Request
Add a Status dropdown field to the ticket creation form in the Atera RMM dashboard, allowing the technician to set an initial status at the time of ticket creation rather than defaulting all new tickets to "Open."Current Behavior
All tickets created from the dashboard default to "Open" regardless of context. There is no way to set the status during creation — it must be changed as a second step after the ticket is saved.Requested Behavior
When creating a ticket from the dashboard, the technician should be able to select a status from a dropdown at creation…2 votes -
API Enhancement: Add 'LastInternalComment' and 'IsSolution' Properties
We request two specific additions to the API to improve ticket management and documentation:
Ticket Endpoint: Add a LastInternalComment field (similar to the existing LastEndUserComment).
Comments Endpoint: In GET /api/v3/tickets/{ticketId}/comments, include the boolean status IsSolution for each comment object.
Context & Why this is useful:
LastInternalComment: We need to quickly see the status of a ticket based on the last technician note, not just the user's reply. Currently, we have to download all comments to find the last internal update.
IsSolution: When syncing tickets to a knowledge base or sending final reports to customers, we need to programmatically identify which specific comment solved the issue. This data exists in the UI but is missing from the API.
We request two specific additions to the API to improve ticket management and documentation:
Ticket Endpoint: Add a LastInternalComment field (similar to the existing LastEndUserComment).
Comments Endpoint: In GET /api/v3/tickets/{ticketId}/comments, include the boolean status IsSolution for each comment object.
Context & Why this is useful:
LastInternalComment: We need to quickly see the status of a ticket based on the last technician note, not just the user's reply. Currently, we have to download all comments to find the last internal update.
IsSolution: When syncing tickets to a knowledge base or sending final reports to customers, we need to programmatically identify which…
6 votes -
Dark Mode for Web app and iOS
Are there plans for native dark mode for both the iOS app and web interface?
As IT professionals who staring at screens all day, this would help reduce eye strain day to day and align Atera with modern tools that already support dark mode.
Ideally:
iOS could follow system dark mode
Web could include a simple toggle or follow the system default
This would be a great quality-of-life improvement for daily use.2 votes -
Default Remote Access Option (No Warning)
The Default Remote Access Option allows one to change from Splashtop to AnyDesk/TeamViewer/ScreenConnect.
The problem is, an admin can change this without warning. It provides no warning or confirmation or context. It immediately just deploys AnyDesk etc. to all agents causing popups on Macbooks and security alerts and mass panic.
Please can you consider a warning confirmation dialogue before this setting is changed or updated? Should be a quick small change hopefully.
28 votes -
add column for security status for what AV is on the device vs look at device only
add a column for the security piece to show what security software is on the device. Currently you have to drill into the agent itself.
6 votes -
when replying to a ticket from an email client as the agent, the comment is not added into the ticket.
when replying to a ticket from an email client as the agent, the comment is not added into the ticket.
For instance, emails to helpdesk@domain.com get sent to atera. A helpdesk manager replies to the original email within their email client rather than in atera. Atera does not properly ingest this as a new comment, even though the helpdesk@domain.com was CC'd. Also, when the customer responds to that helpdesk manager email, atera creates a new ticket rather than merging from the original ticket. Freshdesk handled all these scenarios with ease. Atera is frustrating to deal with for ticketing. Much more focus needs to be put into the ticketing aspect.when replying to a ticket from an email client as the agent, the comment is not added into the ticket.
For instance, emails to helpdesk@domain.com get sent to atera. A helpdesk manager replies to the original email within their email client rather than in atera. Atera does not properly ingest this as a new comment, even though the helpdesk@domain.com was CC'd. Also, when the customer responds to that helpdesk manager email, atera creates a new ticket rather than merging from the original ticket. Freshdesk handled all these scenarios with ease. Atera is frustrating to deal with for ticketing. Much more…3 votes -
secure boot Filter
Filter devices by their secureboot status (enabled / disabled).
3 votes -
Ticket rating submitted trigger (any)
It would be nice to have a trigger in Ticket automation rules for any rating posted. That way we could notify the technician when they receive a rating and they could go and read it.
2 votes -
New Tickets page UI - Feedback [Q1, 2026 Feature release]
Hi everyone — we’d love feedback on the new Tickets page UI (the redesigned, configurable table).
What’s new (vs old Tickets page):
- Detailed vs Compact view (Compact = more rows per screen)
- Show/hide columns
- Reorder columns
- Sorting + saved views
- New columns: Approval status, Created date, Last action date, Parent/Child tickets
What we need from you:
- Reply with anything you’ve noticed, but if you can, use this quick format:
1) Your setup
- Detailed or Compact?
- High-volume queue or occasional triage?2) What works
- What’s better than the old page?
- Missing columns?
- Too many clicks?
- Anything confusing in the table behavior?3) Views + sorting
- Are saved views and sorting doing what you expect?4) New columns
- Is Last action date useful? Created date?
- For approvals: is Approval status clear enough (Pending / Denied / Partially approved)?5) Bugs
- Please post them here or DM me on the Community with the support Ticket ID so we can follow/escalate/fix.If you’re short on time: 1 win + 1 pain + 1 request is perfect.
++
Dima L
Technical Product Marketing Manager
AteraHi everyone — we’d love feedback on the new Tickets page UI (the redesigned, configurable table).
What’s new (vs old Tickets page):
- Detailed vs Compact view (Compact = more rows per screen)
- Show/hide columns
- Reorder columns
- Sorting + saved views
- New columns: Approval status, Created date, Last action date, Parent/Child tickets
What we need from you:
- Reply with anything you’ve noticed, but if you can, use this quick format:
1) Your setup
- Detailed or Compact?
- High-volume queue or occasional triage?2) What works
- What’s better than the old page?
- Missing columns?
- Too many clicks?…3 votes -
New Patch automation page
It does not appear that the new format for creating/editing automation profiles is saving the email for notifications.
2 votes -
Improve Handling of Security intelligence updates (KB2267602)
Currently the Windows Update setting in the Atera Configuration policies are to allow local updates or disable all local settings. The problem with the latter option is that it also disables the automatic updating of Security intelligence updates (KB2267602). Every device will perpetually show as needing that update since Microsoft re-releases it multiple times a day. More info here: https://www.microsoft.com/en-us/wdsi/defenderupdates
I propose the following:
1) Add configuration options under the Atera Configuration Profiles for the Security Intelligence Updates. The most important one can be set with this PowerShell command: "Set-MpPreference -SignatureUpdateInterval <hours>". By setting this, updates for KB2267602 should automatically be checked and installed automatically at that interval even if the normal Windows Update Schedule is disabled. There are also options for scheduled day and times, but the interval setting should run independently of that.
Yes, we can create an IT automation profile to install definition updates daily or multiple times a day, but it clutters up the automation run history log.2) Exclude KB2267602 from the available patches indicators. (Or at least have an option to do so) . You could also add it as a separate definition updates indicator column that could be turned on.
3) Add the most recent definitions update version and date to the device OS and Security page
4) In addition to the all or nothing Windows Update settings in the Atera Configuration policies, let us pick an advanced option with all of the same knobs that are available in group policy: https://learn.microsoft.com/en-us/windows/deployment/update/waas-wu-settings
Currently the Windows Update setting in the Atera Configuration policies are to allow local updates or disable all local settings. The problem with the latter option is that it also disables the automatic updating of Security intelligence updates (KB2267602). Every device will perpetually show as needing that update since Microsoft re-releases it multiple times a day. More info here: https://www.microsoft.com/en-us/wdsi/defenderupdates
I propose the following:
1) Add configuration options under the Atera Configuration Profiles for the Security Intelligence Updates. The most important one can be set with this PowerShell command: "Set-MpPreference -SignatureUpdateInterval <hours>". By setting this, updates for KB2267602 should automatically…4 votes -
SLA Condition for ticket automation
Create a condition based on the SLA remaining - i.e. SLA remaining is 2 hours, then we can configure an action such as sending an email based on that SLA. Currently to do this, we have to use your BETA Hours since created ticket, but this doesn't work well with dynamic SLA times.
2 votes
- Don't see your idea?