- or
No existing idea results
- ~ No ideas found ~
4743 results found
-
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…
4 votes -
Patch management
To be able to schedule Patch management tasks, this would be useful for Mac devices that require Upgrade patches to be run via Patch management instead of IT Automation profiles.
This workaround is useful for Mac devices that are offline, in order to help automate pushing Upgrade patches
85 votes -
Label printing for assett management
Add the ability to print asset management tag labels for managed assets.
70 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
-
secure boot Filter
Filter devices by their secureboot status (enabled / disabled).
2 votes -
Slashtop Chatting
Have the option to chat with end users through SplashTop without having to remotely connect to their machines.
7 votes -
Use multiple monitors at the same time with AnyDesk.
Use multiple monitors at the same time with AnyDesk.
3 votes -
Under the Admin/Settings/Agents tab, under the Prevent agents from being uninstalled on devices it will be nice to have a special username
Under the Admin/Settings/Agents tab, under the Prevent agents from being uninstalled on devices it will be nice to have a special username/password for device to allow uninstallation. This will allow the agent to remain securely installed on the device.
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 -
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.
67 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
-
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 -
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 ...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
-
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.
6 votes -
bulk
Please add option to bulk assign folders\site to devices, this is already on every other MDM it can be done easily via CSV on intune for example. We want the same option here in Atera, so if lets say I need to switch 300 devices to a more "aggressive" patch profile I dont need to manually assign them 1-by-1.
1 voteHi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
You can also follow this in our Public Roadmap.
Best regards,
The Atera Team
-
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
- Don't see your idea?