- or
No existing idea results
- ~ No ideas found ~
5040 results found
-
Ticket Automation Rules - "ticket created" email - stop email loops
The current "Ticket Created email" automation rule works well most of the time. However, when we need to get a third-party support company involved, they often have an equivalent system that sends an automatic "Ticket Created" email, that creates a new Atera ticket, and sends back a "Ticket Created" email, ad infinitum. In our case we had 18 new tickets created in the seven minutes until we noticed the loop. If someone had not been looking at the Unattended queue, it could have been many more.
My idea is for Atera to be able to identify a "Ticket Created email" loop,and add the new incoming "Ticket Created" email from the third-party system to an already created ticket, and NOT send a Ticket Created email.
A possible way of identifying this loop is multiple emails in a short period from a particular email address, with a subject that is the same, except for an increasing number (ie their ticket number)Note: this is specifically for occasions where we have not previously dealt with that third-party support company. Obviously once we have dealt with a third-party support company, we then know that that particular company sends out "Ticket Created" emails, and we can add their email address to the "Ticket Created email" automation rule as an exception.
The current "Ticket Created email" automation rule works well most of the time. However, when we need to get a third-party support company involved, they often have an equivalent system that sends an automatic "Ticket Created" email, that creates a new Atera ticket, and sends back a "Ticket Created" email, ad infinitum. In our case we had 18 new tickets created in the seven minutes until we noticed the loop. If someone had not been looking at the Unattended queue, it could have been many more.
My idea is for Atera to be able to identify a "Ticket Created email"…
4 votes -
set a script-based check run interval
Be able to set the 'run interval' of a script-based check. We are running into issues battery life on laptops and hitting api limits
3 votes -
Need a device filter for assigned threshold profiles
Need a device filter added for assigned threshold profiles. We need to easily filter devices to see which may not have a threshold profile assigned at all. Or that do not have the correct threshold profiles assigned. And then be able to add them via a multi check box.
3 votes -
Custom Assets View
Custom Assets
Should be able re-organize which fields shows in the dashboard, instead of the default Name, Type, Folder and Contact.
Also an option for the date field to have an alert. For example if you are tracking support services renewals for the customer, it should alert you when renewal is within 30 days.
15 votes -
show device count on customers
The customers table should show how many devices each customer has, and optionally how many are online. Bulk onboarding agents is more painful than it needs to be without this.
3 votes -
Create ticket trigger under ticket automation rules for patching
Trigger for generating a new ticket if patches are applied manually through devices tab by a technician. Seeing as this is a manual action by a technician and not done through automatic patch management it would warrant a ticket being generated for a specific agent/contact with a relevant time entry.
4 votes -
Customizable Availability Monitoring
The ability to get an alert if a device is offline for so long, like say an hour, instead of getting an alert for a device going offline, when it is only restarting or something similar
2 votes -
knowledge base Report
Create an option to pull reports on knowledge base as to who viewed and how much times the articles was viewed
5 votes -
New internal note alert
Alert by email the technician that a new internal note is added to his ticket.
23 votes -
Author of Knowledge Base Articles
It would be good to know the author/source of a Knowlege Base article. We have several contributors and it would be good to know the source to check validity, follow up with them for clarification, reward those that are frequent/prolific contributors of KB articles. We can already see the creation date. It should be fairly easy to add a field for Author/Creator of KBs.
1 vote -
manage Microsoft 365 users directly from Atera
It would be great to be able to manage Microsoft 365 users directly from Atera. Doing things like Password Resets, Create new users, Adjust / Add licenses, Email forwarding etc, instead of having to login to each customers Admin portal everytime. This can become extremely time consuming.
6 votes -
Better structure to the KB
It would be nice if we could build a deeper KB tree. Currently it can only be two layers deep.
L1: Category
L2: Section
It would be nice if we could go at least 1 layer deeper and have subsections.9 votes -
When assigning agents to tickets, show logged in user in dropdown.
The dropdown when assigning an agent to a ticket should show the current user, as only this way we know which device has the problem (as users don't always work at the same PC)
1 vote -
Dateien an Ticket hinzufügen
It would be convenient if files could be attached to a ticket.
A current workaround is to create an internal note and then attach the file, but then it becomes necessary to search for the file in the ticket history whenever the ticket becomes longer.1 vote -
ticket activity messages
I think it would be very useful that ticket's history section reflects which Rules has been applied (appearing on history as the rule's title), and not just the action. This would work as a kind of "debug", helping us to confirm which rules are really applied on each scenario and accelerating/helping a lot our learning curve.
1 vote -
Date & Time Format
Option to change the date and time format to 24 hours and dd.mm.yyyy.
8 votes -
Set Program to uninstall upon next use
It would be great to have the ability to select a program from the device inventory to uninstall even if the device is currently offline. The task would que for the next time the device is available.
12 votes -
Alerts for new ticket and ticket replies
You know how alerts will play a sound when it happens? That would be great if you could make tickets do the same thing. If someone creates a ticket I would like to be able to turn on a sound notification just like the alert sound settings. I already get ticket notifications on my phone so I do not feel like this is would be hard to integrate into the web dashboard.
1 vote -
Agent chat
Please make an option to disable and enable automatic ticket creation the Agent chat that create ticket after two minutes of conversation.
Please, We want to chat with the user and leave the user create the ticket or the IT to create the ticket manually.
We need this option to interact with the user with no limit, please make this happened.
1 vote -
misfunction on Action "Send email to Technician"
Misfunction detected on following scenario:
Rule Trigger: Ticket Requester Responded
Conditions: no conditions
Action: Send an Email To TechnicianThis action only works when just one of the implied users is a Technician. But when implied users are both Technicians, this action doesn't works.
I identified this as a misfunction because on complex helpdesk structures it's needed one Technician to create an incident specifically for other higher level Technicians (incident not related with any "normal" requester, but specifically for internal IT troubles between different Technicians). This way, the important thing here is not related with the Requester role in any way, but the email of AssignedTechnician in order to execute the action correctly.
Misfunction detected on following scenario:
Rule Trigger: Ticket Requester Responded
Conditions: no conditions
Action: Send an Email To TechnicianThis action only works when just one of the implied users is a Technician. But when implied users are both Technicians, this action doesn't works.
I identified this as a misfunction because on complex helpdesk structures it's needed one Technician to create an incident specifically for other higher level Technicians (incident not related with any "normal" requester, but specifically for internal IT troubles between different Technicians). This way, the important thing here is not related with the Requester role in any…
1 vote
- Don't see your idea?