785 results found
-
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 -
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 votes -
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 -
Option to provide an offer to a customer
Current setup:
It is possible to raise tickets through the customer portal.
Within these tickets you can ask some questions by input fields but at the end all of these look very similar.
Example:
Ticket 1: I am not able to start Microsoft word
Ticket 2: Can you please provide an offer for a new monitor
Ticket 3: Can you please provide an offer for updating all my computer to windows 11Problem:
When using the example in the description above the "Ticket 1" is the default ticket which you receive.
"Ticket 2" is a normal hardware offer whereby "Ticket…1 vote -
Impact
Would like the ability to edit the SLA section and provide my own Impacts instead of using the default ones.
Also an ability to delete ones we are not going to use.
16 votes -
Allow Snippets in Emails for Custom Ticket Fields
I'd like to be able to use snippets in email tickets that are dynamically linked to custom ticket fields that I've created.
14 votes -
Email template be applicable to the reply section
Would like to see the possibility of an email template be applied to the reply section automatically.
This is a great idea to make sure the ticket number and ticket title will automatically be added to the replies.
Even moreso when the same user has multiple tickets, to be able to differentiate between them.2 votes -
gestion temporalité tickets
Il serait intéressant d'avoir une possibilité de gestion temporelle des tickets.
Par exemple, fermet automatiquement les tickets ouvert ou en attente qui n'ont plus eu aucune modification depuis 6 mois.
Ou bien pouvoir se dire, je met ce ticket en attente mais il doit se réouvrir tout seul dans deux semaines pour tel ou tel raison.2 votes -
Change the user that the ticket is held under.
For example, we have a user which regularly forwards tickets to us that are generated from an email forward. But since the ticket is then put against the person we received the forward from, we're unable to email the actual user the ticket should be held against within the ticket.
2 votes
- Don't see your idea?