780 results found
-
Ability to change To: in ticket
Ability to change the assigned To: in a ticket without having to create a new contact each time.
We get tickets that are for other users, and it would be helpful to have the option to modify the To: field in the response, or remove the original requester and only have the user the ticket applies to in the message string.
1 vote -
Show next scheduled touch date when viewing list of tickets
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.
2 votes -
Ticket Snooze
It is possible to schedule a ticket for the future.
It is possible to snooze an alert.
It would be nice to be able to snooze a ticket until a future date -or for a period of time- that way you can get it temporarily out of your queue, but still follow up with the user later.
5 votes -
My Tickets view
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.
3 votes -
Sorting Tickets by Last Response
We often will modify a ticket priority or type in basic triage, but in doing so, it messes with the order or tickets if sorted by last modified date. It would be great if tickets could be sorted by last comment date so we can review tickets that don't have responses on them quickly.
19 votesNice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Ticket email automation
When a Ticket is closed can the email response include the last comment made on the ticket? Whether it be from the Customer or the Technician?
My process is the update with final notes, press “Send Reply”, then I set the Ticket Status to either Resolved or Closed. I don’t see a way to set Resolved and have it Send Reply all in the same action.4 votes -
Conversation / Effort Thread
The email / reply section of the ticket, is the only thing that appears as part of the conversation thread. Any time / notes posted, does not show "in line" as part of the thread.
Autotask / ConnectWise, both put ANY effort (notes / email) in order as part of the entire conversation thread. Not having the time/notes show is a waste of effort filling it out. ideally, the email "reply" section should be REMOVED and ANY effort, including an email to the affected user, should be time tracked and part of the thread (ala ConnectWise/AutoTask)
6 votes -
Increased visibility of ticket status - such as the whole line being shaded differently
With the new ticket view it is harder for the support team to differentiate on the list which tickets are "awaiting customer response" or "awaiting technician response" as there is a just small circle of either green or purple next to the status. We would like tickets where they are awaiting our reply to be obvious at a glance to prevent a reply from being missed.
5 votes -
Filter Tickets by Last Modified
It would be helpful if we could filter by Last Modified - e.g. Last Modified last week but not this week, so we can easily see if there are any tickets that we've missed out on updating.
5 votes -
Pin a ticket
Pin a ticket to the top of the list.
4 votes -
Add Ticket Title to Ticket Timer
It would be great if the Ticket Title could be added to the Ticket Timer at the top so that when it is easy to see which ticket the timer is for.
Currently it only shows Ticket number and the time accumulated.
1 vote -
Search tickets by date.
Instead of only showing created 9 weeks ago. Can we add in the exact date it was created?
2 votes -
Quickly See Time Entries/Updates Quickly on Ticket
Under the ticket, if there is another technician, he can quickly check what has been done on the ticket, how many hours. (doesn't want to go and click on "time entries" etc - wants it already available on the ticket itself).
7 votes -
Auto Tag to affect SLA
Auto tag to automatically affect the SLA and it can not be set in admin, also that it will affect the impact
3 votes -
Schedule a single script at the device level or in tickets
Scheduling a script run right at the device (or even inside a ticket where you could pick the device!) would be ideal, with users in meetings frequently we could schedule patch removals or other items requiring a reboot for post meeting or known free/available time - it would be ideal as well to get an automated ticket update saying it had run and completed or failed
5 votesNice! The feature you requested is being
reviewed by our product team. We’ll keep an
eye on the number of votes, and let you know if
a decision is reached to implement. Thank you
for being a partner in our process! -
Helpdesk agent improvement
When we see the ticket status all look similar and I'm facing difficulty to understand ticket status. I recommend, for new ticket and Waiting for Technicians response status shows more brighter with red color, so that we can easily understand.
1 vote -
ticket tagging
Feature request;
1) option to make tagging mandatory when creating a new ticket
2) option to limit the rights to create new tags (only 1 or 2 users can create new tags)
3) option to disable manually typing in tags. (ONLY possible to use drop-down when creating a ticket)2 votes -
Create ticket for customer without selecting contact person
I need the ability to create a generic ticket for a client for internal use, I don't want the ticket to show on the client portal.
5 votes -
Calendar Integration
We should be able to see an indicator that something was already scheduled. What's the purpose of having a shared calendar for Atera if we can't tell if a ticket has a Calendar entry?
1 vote -
Ability to select Source = API for ticket automations
I feel like I'm the only one that ever uses the Atera API because I constantly find it lacking or half baked into the entire system.
The ability to create a new ticket via the API works as intended. However, currently you cannot do any ticket automation relating to the Ticket Source = Api.
The functionality is there in the back end, because when the ticket is created via the API, the ticket DOES in fact have the attribute of [TicketSource] => Api.
You simply cannot select Api as an option in the GUI for Ticket Automations.
Chat revealed this…2 votes
- Don't see your idea?