708 results found
-
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.
216 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.
61 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,…15 votes -
Adding the option to append the date of the ticket creation to the ticket number.
We are in the process of onboarding with Atera and noticed that the ticket numbers are simply an incrementing number.
Some of our users appreciated the old system's ticket numbers including the date that it was created. an example being 15-11202025, this way it can be identified as the 15th ticket created on 11/20/2025.
Can a checkbox option be added in the settings for companies to choose to add the date to their ticket numbers?
2 votes -
Ability to schedule already open tickets
I have recently discovered that a few clients will have a ticket open already and will not reply for a few days and then ask to have the issue looked at on a specific day.
This wouldn't be too bad if there wasn't already key details and notes in the ticket already, and closing and opening is just tedious as the ticket isn't technically closed/resolved.
I feel like a feature to schedule an already open ticket to automatically be closed and reopened within a specific time frame would be amazing.
It doesn't even need to be necessarily closed, just disappear…27 votes -
Deleting comments
Ability to delete comments.
If an external email has dropped inappropriate content into a ticket, we should be able to delete that ticket comment to remove the content.
41 votes -
Allow for customization of columns on ticketing screen
On the Ticketing page the columns are locked to the default fields. We don't utilize the SLA field within our organization; and the new sentiment column is also irrelevant.
Allowing the end user to change what is displayed on the ticketing dashboard would allow for extra space for fields that are relevant, like allowing for longer ticket titles to be displayed.
351 votes -
Save Public Reply Without Emailing
It would be nice to have an option to save a "Public reply" to a ticket without initiating an email to the contact, this way the notes are visible to the Client contact in the customer portal but we don't have to necessary spam the contact with technical notes via email.
14 votes -
Email technician when they have been @ tagged on an internal note of a ticket
When you make an internal note and @ tag an engineer, That technician should receive an email saying "You have been mentioned on a ticket (hyplink to ticket)"
330 votes -
The ability to see ticket audit trail in mobile app
The ability to see ticket audit trail in mobile app That way you can see who put the ticket in, if it was another Admin or an actual user, and can also see if it was merged from another ticket, etc.
6 votes -
expose CC in API
Currently the API only exposes main contact per ticket and comment. it would be useful to see or use the cc field in tickets via the API.
1 vote -
Request to Include Custom Fields in Ticket & Customer Dataset
I’d like to request an enhancement to the current API/UI data exports. At the moment, custom fields created for tickets and customers aren’t included in the returned dataset, which limits their usefulness—especially for reporting, automation, and integrations.
Having access to these custom fields (both in API responses and in any exportable datasets) would significantly improve our ability to build accurate workflows, dashboards, and documentation. These fields often store critical business-specific information, so including them would be extremely valuable.
1 vote -
Request for Larger Page Limits When Querying Tickets, Customers, Alerts, etc.
I’d like to request an enhancement to the API/UI regarding data retrieval limits. Currently, when querying items such as tickets, customers, alerts, and other objects, the page size limits are quite restrictive. This creates unnecessary overhead, especially for larger environments where we need to pull or review substantial datasets.
1 vote -
approval
It would be awesome if we could automatically require all tickets from a company go to the main contact for approval requests! Manually doing this is tedious and often missed!
1 vote -
Export tickets to pdf
the objective would be to be able to export a summary of the intervention in PDF in order to keep a paper trail signed by the client
16 votes -
ticket timer auto stop
issue:
Tickets that get clicked on get a timer started (good feature). When we click out of the ticket of when there is a response given, the ticket timer should stop (requires manual pause). 99% of the time no one is going to pause the time.Feature required:
Auto pause the ticket timer after there is a response added to the ticket or if you happen to click on another section of Atera.6 votes -
Restricted Form with Automated Sub-Tickets
We'd like a form to be visible to only one department. For example, when Human Resources needs to report a new user to IT, they open a ticket. They need a dedicated form. This form will contain custom fields such as first name, last name, etc., and there will be multiple modules (IT Equipment, Applications, etc.), each with custom fields: computer, telephone, telephone number (for IT Equipment), World, Excel, etc. (for Applications).
The parent ticket is created with the request for the parent form, while for the subforms, as many tickets as there are forms are created, and these will…1 vote -
Color coding options for different ticket status
Color coding options for ticket status's.
27 votes -
"ticket type"
The ability to add Ticket Type as a column in the initial tickets view screen.
1 vote -
Ability to edit Internal Note on ticket
I really wish we had the ability to edit an internal note. In the event of an error, it would be nice to be able to hit an edit button and change an internal note.
48 votes
- Don't see your idea?