It would be greate if the SLA definition could also be set to fields like Ticket Proiority or Ticket Type instead only to Ticket Impact.

In some cases Incidents must be handled differently than a change or a request even if it have the same Ticket impact - like Minor - or those fields gets hide in the ticketing portal.

Ability to add custom drop down options for the status of tickets. This will allow to use Atera as project management tool as well.

When on a ticket, it'd be a good idea to pause a ticket than outright stop it.

the ability to schedule an existing ticket for a later date

Currently if we want to use the APIs to pull certain tickets or time entries for a particular client and/or a particular timeframe, we have to pull ALL THE TICKETS in our Atera account (which takes a long time, and generates a lot of traffic to Atera's servers).

Can you please add additional criterias to avoid all this extra traffic and make the API calls faster?

Time Entries and Tickets search:
* Before date-time
* After date-time
* Customer ID
* String in comments (all words, or any words).

Thank you!

Currently there is no way to quickly view/edit timeentries within a timeframe (all of for a client in particular). The manual process to do this is incredibly painful. (go to timesheet, and open manually each ticket, go to time entry, and pinpoint the time entry, save, re-run timesheet, etc.).

Please add an screen to review all time entries.
1) List the time entries (filter by timeframe, customer, billable or not)
2) Allow to quickly edit a time entry
3) Display total

It would be helpful to have ticket templates/ticket option type for the end user creating a ticket.

For example, the end user is requesting a new hire setup. They would be able to go to create a ticket and have the option to select "New Hire" ticket. Then, fields would appear that have been customized by the admin.

On the other hand, maybe even having an option create a form for end users to fill out and generates a ticket.

When you merge tickets alerts, no information is left on the ticket so we don't know what it is referring to. Useful to add the body of the ticket or the title of the ticket/alert. Or maybe a link to the other closed ticket.

When viewing the list of tickets, it would be very helpful to see that next scheduled touch date. That in conjunction with the activity status would make the "Tickets" view much more usable.

Option to assign multiple contacts to a ticket.
A single issue in a ticket can touch multiple users/contacts. When an ticket is scaled up from incident to problem. or when multiple people experience the same issue. I would like to be able to add more contacts to an issue.

It would be nice to have the ability.. or if it came out of the box, to have a view in tickets called My tickets so that technicians can see a list of all the tickets they are assigned to...instead of creating a view for each tech.

Ability to set Technician status to away, vacation, or project so that they are not assigned tickets during this time.

Split ticket in activities. every activities should have a different contract. like on site and remote support have different price but ticket is the same.
Then after ticket is closed contract nedd to be unchangeble.

If we are going to work in an ITIL compliant environment, I think you should be able to change the default ticket type to be REQUEST. More items come in as Service Requests than they do as INCIDENTS.

Users sometimes email in with info only in the subject, or they set out of office with no info in the body. If this occurs all we see in the ticket is a blank entry.
Solution would be to include the email subject.

Change management for tickets: I want to integrate it into Atera so we can manage instance requests and changes because at the moment we don’t have a change platform. A ticket but you need to have a manager approval on there. For bigger tickets that need to be approval. https://community.servicenow.com/community?id=community_question&sys_id=cc8e16e7dba41f442328f3231f9619d9

When closing the ticket - it throws up a box where you can enter the fix/resolution for the ticket. Perhaps add tagging options to make it searchable. This would be helpful for tickets with long threads of communication between the user and technician and simplify finding the resolution for an issue.

When creating a ticket the end user may have a screenshot of the problem they'd like to share, allowing image attachment capabilities to the API would give them the option of need be.

While entering time in a ticket, add the ticket status drop down to close or change the ticket status to reduce the amount of steps needed.