704 results found
-
API for emails to pull tickets in via API calls rather than forwards or SMTPAuth
An option to integrate with email providers i.e. Microsoft via API calls rather than forwards.
This would allow emails/tickets to be pulled in fast, secure and minimises the amount of issues that can arise from email forwards and can help prevent ETP systems from double scanning emails that have already been checked (reducing hops and preventing further delivery issues)
1 vote -
Ability to turn off ticket tabs
We would like the ability to turn off ticket tabs - we don't find them useful as they are presently.
2 votes -
Ticket Forms, under type, Dropdown with dependencies, it would be nice to multiple child levels.
When creating new ticket forms and selecting a dropdown with dependencies, there is only one child layer option. It would simplify our setup if we could include multiple child levels. I have attached an example of the current option and the desired option.
2 votes -
Button to go to 'next' and 'previous' ticket
There's an idea on this, but I am posting this as I feel the other ones are not really explained thoroughly.
I think there should be the option of -- if you're seeing your ticket 'view', to have the option to go to the next ticket.
on my organization, we open tickets to track certain stuff for records, just like any other else, but there has been the occasion where I have over 10+ tickets that I want to 'close' but I also want to Open the ticket, to see the last update I made, add an extra comment such…
1 vote -
tabs
Tabs should close when tickets are resolved/closed - There are filters to check on old tickets (closed/resolved).
Alternatively, the option to turn off tabs altogether would be welcome.
1 vote -
Forward email from non english Outlook to create a ticket
I'm sorry to inform you that all people are not using english version of outlook or gmail. Please, be nice with us, and fix the forward email to create a ticket at the requester name (and not the tech).
1 vote -
New Ticket UI Saving View
Hi Atera Team,
While the recent UI changes to the Tickets page have been generally positive, I’m running into a significant issue with the “Save View” functionality.
Currently, the “Save View” button does not retain any customization related to hidden columns, column rearrangement, or column width adjustments. Although I appreciate the ability to customize the new ticket layout—such as hiding unnecessary columns like AI, Sentiment, etc.—these changes are not being saved. As a result, the default view continues to feel cluttered and overly busy.
This limitation is having a noticeable impact on our workflow. Each time we navigate back to…
1 vote -
Assigned Group Feature Needed
Hi, I need a way to group tickets by assigned category, such as Security, Networking, Printers and Scanners, Hardware, Software, etc. This would allow for better analysis of the data. Is it possible to add this feature? Thank you!
1 vote -
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?
4 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.
2 votes -
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.
2 votes -
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!
2 votes -
"ticket type"
The ability to add Ticket Type as a column in the initial tickets view screen.
1 vote -
standard ticket filter
Ticket lists often start with standard filter Status:open/pending
Thats not really helpful because of our self added statuses, like "waiting for material (pending)
So ist would be better, instead of filtering status:open/pending, it would filtering status of type: open/pending
1 vote -
Tagging knowledge to tickets
Have the option to tag related existing articles to existing tickets customers have opened.
Allowing managers or leads to tag possible related articles to tickets to expedite troubleshooting or client resolutions.
Might even suggest a step further, where you can suggest an existing article as a built in response within your reply. Essentially, "Hey customer- have your tried #tag existing article here, as a resolve?".1 vote -
change public entry to be a private entry
We email into tickets renewals for services from suppliers then email to the customer on this ticket to advise on renewal pricing.
If we just change the ticket to the customer they see the history from the original entry.
We need to be able to change this to a private entry so the customer does not see the whole email chain.
1 vote -
Sort by activity status
On the tickets page, please add the ability to sort by activity status, add new columns, for example date created, ticket age and the ability to simply click on the title of the columns to sort it instead of using filters, and instead of having a small coloured dot, it will be more noticeable if the entire text is highlighted.
1 vote -
SLAs based on ticket type and custom fields
Ability to setup SLAs based on ticket types, tags, and custom fields.
1 vote -
Different default template for tickets created by technicians
It would be nice to have different default form templates for tickets created in the user portal vs. created in Atera by a technician without the tech having to remember to change the template. This would give the ability to add more technical fields automatically when the ticket is created by a tech. It would also allow more customization of ticket automation rules based on whether the ticket was created by a user or by a technician.
1 vote
- Don't see your idea?