- or
No existing idea results
- ~ No ideas found ~
5062 results found
-
Allow agent<>user machine relationship to be updated via API
The API is a great way to update many items quickly.
To be able to update the agent's relationship with a user via code would be a real bonus.
Currently facing the prospect of updating this manually fills me with dread.
1 vote -
Client Ticket Assignment
Auto Assign Tickets, to Clients, based upon Subject Header of the email sent. (Not only the email address that it is sent from.)
6 votes -
Ticket Rows too large on screen, need a way to customise layout
Size of the row that each individual ticket takes up is too big, can only fit about 8 tickets on a 1080p screen
it still manages to also cut off the title when its too long though!
need a way to change the layout of the ticket
2 votes -
Notes in app
A way to add notes to a customer in the mobile app.
6 votes -
Allow Linux computers the ability to be a monitoring agent for SNMP, Network Discovery, etc. devices?
We would like to put our own linux system at a users site to monitor SNMP instead of relying one of the clients systems.
3 votes -
SNMP v3
It would be a good idea to add the functionality to be able use Network Discovery to scan devices using SNMP V3.
All our switches are configured with SNMP v3 only due to security reason and adding all these switches for monitoring has become a challenge.33 votes -
Two Way SplashTop Audio
I got a request for two way audio via the splashtop app.
1 vote -
Webroot actions appear in recent processes
When deploying webroot via the atera option there is no record for that action under recent processes.
I could get a record if running it as an independent script but that feels pointless when it's built into Atera4 votes -
System shutdowns should either report under the "Last Reboot Time" or in their own category.
I was told they are not the same, but it is basically the same. You want to know when the system was rebooted/shutdown. I had a client that hadn't rebooted, but they shutdown their machine every night. The system reports this as uptime, which is very wrong.
2 votes -
Provide the ability to run a report with all customers selected
I would like to run a report for all customers selected at once. Then have the ability to export as a .csv file so I can analysis the data to figure out what we have in the field.
2 votes -
Add subscription renewal date to subscription page
It would be helpful to know when our next subscription billing date is on the subscription page itself. Right now it just shows Monthly and Yearly fee along with payment info. I had to contact support to see when my next billing date would be.
2 votes -
Change Activity Status as an action for the ticket automation rules
Change Activity Status as an action for the ticket automation rules
2 votes -
Change email response when "Login using activation link" is clicked
The email sent is unbranded and looks suspicious.
It would be good to create our own branded email and provide further information such has details on how to log a ticket correctly1 vote -
Tickets from Alerts auto-requestor-assignment
If there is no user assigned to a "machine causing an alert", set "requestor" to a Techician or System.
Current automatic behaviour is to set the first (alphabetically) contact from the affected Site to the alert/ticket .1 vote -
tag search
Adding tags to different tickets are not getting recognized by the search engine.
It would be great if you can search for ticket-tags just like in the knowledge base with "#tagname" or if there is a free-text field in the filter section and not just checkboxes for the tags.
And on top of that in the filter section the tags are not in alphabetical order, this would help too!greetings
2 votes -
Integration with supremo
Integration with Supremo (as team viewer)
6 votes -
Alert For Expiry Date In Assets
Alert options for expiry dates added to assets.
3 votes -
usecure
usecure.io integration https://www.usecure.io/
1 vote -
datto
Integration into Datto backup and Kaseya spanning would be a nice to have. Not critical.
8 votes -
Tickets are duplicating due to Subject line
Instead of checking the Subject line to prevent tickets being duplicated, instead insert a ticket ID into the body and check for that ticket ID in the body to prevent tickets from duplicating due to replies not having a specific subject.
Cherwell does this, it places the ticket ID into the body, For example, within the body, you'll find the Ticket ID written out on the bottom of an email - {CMI 43EF84993H2}
Cherwell scans each email's body for the ID and places/groups that email into the correct ticket. If it doesn't contain the ID within the thread of emails, it generates a new ticket. If the ID is so old and resolved, it creates a new ticket.
Why I bring this up is because Atera tickets are duplicating whenever someone alters the subject line with either a "RE:" or a "FWD:"
Atera depends on the subject being identical to the first subject line that initiated the email OR keep the ticket # in there, which is only generated if the ticket has been responded to, when you respond within Atera, it adds "Ticket # 1234" to the subject line.Issue with changing the subject is that it creates a new thread for the end user, which is a bad practice because end user also wants the email to be under one email, and not two separate emails.
Instead of checking the Subject line to prevent tickets being duplicated, instead insert a ticket ID into the body and check for that ticket ID in the body to prevent tickets from duplicating due to replies not having a specific subject.
Cherwell does this, it places the ticket ID into the body, For example, within the body, you'll find the Ticket ID written out on the bottom of an email - {CMI 43EF84993H2}
Cherwell scans each email's body for the ID and places/groups that email into the correct ticket. If it doesn't contain the ID within the thread of emails,…
1 vote
- Don't see your idea?