- or
No existing idea results
- ~ No ideas found ~
4722 results found
-
Cancel Ticket Creation Confirmation
When creating new tickets the cancel button is located directly next to the create button. This cancel button doesn't require any confirmation, and immediately cancels and deletes any information entered into the ticket. With a sensitive mouse it is too easy to click the cancel button by mistake forcing the ticket creation process to restart.
3 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…
11 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
-
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.
3 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!211 votes -
"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.
52 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
-
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?…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…
3 votes -
Copilot window obscures device function buttons
On a device page, the AI Copilot windows obscures the Connect, Manage, Copilot, and Create ticket buttons along the top. Similar issue on the Ticket page, etc.
2 votes -
Trouble Ticket Detail Templates
I would like Atera to implement a Ticket Detail Template feature within the New Ticket screen, specifically under the Enter Ticket Details field . This enhancement would introduce a dropdown menu that allows users to select from predefined templates, helping streamline ticket creation and ensure consistency in language, formatting, and technical detail.
How it Would Work:
Dropdown Placement: Above or below the Enter Ticket Details field, a dropdown menu labeled “Insert Template” would allow users to select a predefined ticket detail template.Template Management:
Templates would be configured by Admins in the Admin center.Each template should include:
Formatted text, including headings, bullet points, hyperlinks, and styling (bold/italics)Optionally dynamic fields like [Customer Name], [Device], [Technician], etc., to auto-fill standard variables
User Experience:
When a template is selected, its content would populate the Description field automatically, which the technician can then tweak or expand upon.Markdown or basic WYSIWYG formatting should remain available.
Why This Matters:
Time-saving: No more copying and pasting from external documents or previous tickets.Consistency: Ensures all tickets follow the same structure, improving technician clarity and client-facing professionalism.
Training: Makes onboarding easier for new techs who can follow standardized ticket language and formatting.
Compliance and QA: Helpful for meeting internal documentation standards or industry compliance by enforcing specific data formats.
Example Templates:
Initial troubleshooting checklist
Onsite visit summary template
Firewall install/config notes
End-of-shift handoff summary
Service outage postmortem formatOptional Enhancement:
Allow default templates to be tied to specific ticket types or categories (e.g., selecting “Onsite Visit” from ticket type preloads the corresponding template).I would like Atera to implement a Ticket Detail Template feature within the New Ticket screen, specifically under the Enter Ticket Details field . This enhancement would introduce a dropdown menu that allows users to select from predefined templates, helping streamline ticket creation and ensure consistency in language, formatting, and technical detail.
How it Would Work:
Dropdown Placement: Above or below the Enter Ticket Details field, a dropdown menu labeled “Insert Template” would allow users to select a predefined ticket detail template.Template Management:
Templates would be configured by Admins in the Admin center.Each template should include:
Formatted text,…15 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.
4 votes -
Feature Request: Allow running / re-running ticket playbooks on existing tickets.
Feature Request: Allow running / re-running ticket playbooks on existing tickets (or in a ‘simulation’ mode) so we can iterate and debug complex automations faster without generating new test emails/tickets each time.”
2 votes -
Tabbed or Minimisable devices view / Powershell / SSH sessions
I do a lot of remote PowerShell to work on various PCs. I have to open multiple tabs of Atera to work on different PCs at the same time. I would like the ability to open a remote PowerShell, then minimize it and open remote PowerShell on multiple other PCs at the same time within one window. That way, it can continue to run the command minimized while I work on something else, and can check back on it later to see if it finished.
5 votes -
We need an API to inject a Knowledge base article into Atera
We need an API to inject a Knowledge base article into Atera. Our organization has knowledge base sources in multiple places. It would be nice to be able to pass knowledge base articles from other sources into Atera's knowledge base so that the AutoPilot can use them.
1 vote -
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…2 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.
9 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
-
gili test
this is a test
2 votes -
Network Management Platform Monitoring
Integrate connection to Network Management platforms (ie; Ubiquiti, Cisco). Allow for device update and other notifications directly in Atera. Also links to platform website that opens in another tab directly to the selected site, device or setting. This could also be used for asset management integration for warranty and RMA submition or status.
2 votes -
Remote access approval different approval settings.
Need different approval settings for remote access based on the device type. I want my helpdesk technicians to be required to get user approval to work on their system, but my server admins should not need approval to remote into a server since there is no one at the server to allow the access. This could be based on the role in the platform like Admins can skip the request, while technicians are required to get the approval.
5 votes -
I would love to have more columns in the device search, for example looking for device serial number would be great
Having more options to quick search would be helpful minimizing the time to look into each device detail.
for example I would love to see columns such as, Device serial number, Processor, Memory, MAC addresses ...7 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
-
Can ticket automation do follow-ups and close if no answer?
We've been trying to find a way to implement automated tickets follow-ups (using "activity status" and "hours since status changed") but can't seem to get it to work. Has anyone been able to make it happen? Currently, there is no trigger for Activity Status just Status. We cannot mark the ticket as Pending everytime to trigger this automation. Defeats the purpose of an automation it will have be done manually. I found a reddit article replied by Atera (3 years ago) and still no change. https://www.reddit.com/r/atera/comments/zevva9/can_ticket_automation_do_followups_and_close_if/
1 vote
- Don't see your idea?