698 results found
-
Insert link from knowledge database in ticket response
It would be very helpful to be able to link to an article in the knowledge base in a ticket response, so that the customer is taken directly to the article via this link.
Like NinjaOne
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?
3 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.
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!
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 -
Close Note field
When I'm ready to resolve or close a ticket, I'd like to have a field where I can type a "Close Note". This would get logged like any note, but since it's a separate field, it could be included on reporting. Also, there could be an option to either make the close note internal or public reply (like regular notes).
Alternatively, this could be done by having an option in the existing note section where you could select resolve ticket or close ticket. Then anything entered into the note section on that reply is flagged as the 'close note' and…
2 votes -
Tags via API
Get / amend Ticket tags via API. It would be great if we were able to view/amend/add the tags associated with Tickets
2 votes -
UI Ticket page. My feedback as on reddit.
See my post on Reddit for mock up picture.
/r/atera/comments/1l8qivn/uilikeimachildsidebarandtickets_page/Ticket’s page.
Remove duplication. Text or Icon. PICK ONE!
Contrast on objects. Make things stand out.
Resizing, things should be adjustable. (so we can see useful info.)
Dead space, so much is wasted.
Colour, even colour-blind people can see at least two colours and bits in between.
BAN GRAY! If it’s a primary action make it black or a high contract colour.
Columns would be nice if we could select / make our own page. (we can dream)1 vote -
DateTime or just Time custom field
Currently, there is only a "date"-type custom field. We have need for tickets that also include a start and end time as well. It would be nice to have a time field, and/or a combined date/time field.
1 vote -
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 -
scheduled ticket frequency monthly at specific weekday
It's not smart to set a ticket frequency to a numbered day, because that are changing weekdays.
A schedule like "first tuesday", "second wednesday" or "last friday" would be much more important
1 vote -
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
- Don't see your idea?