- or
No existing idea results
- ~ No ideas found ~
4753 results found
-
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 -
Add "Requires Reboot" to Atera API
At the moment, the Atera UI shows us that a machine requires a reboot, but without running a command against each machine, it is not possible to identify if they require a reboot directly with the API. This would be a very useful feature for the purpose of patching and reporting.
9 votes -
datto
Integration into Datto backup and Kaseya spanning would be a nice to have. Not critical.
8 votes -
Separate File Transfer permission
I do not want any Admin or technician having access to the files and folders of an end-user. So either this "File Transfer" option should be configurable under Permission-Roles or there should be granular permissions for the "Desktop Remote Manage" permission under RMM in Roles. I wouldn't mind this feature to be totally disabled as this can raise a flag in security audits or can cause a management concern where security of data is of topmost priority.
17 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 -
Technician Roles to be more specific define
The technician roles section needs to separate permissions more details. There is already an request for a new permission switch to creating knowledge base with full admin role.
But instead of just that, I recommend it should be more sub-control to all areas, such as knowleadge base, SNMP Templates, Alerts and etc, giving the management a flexible to provide more control to the technician.
Having a technician with full admin rights to manage such areas doesn't make sense. Control need to define well for a technician vs admin. Hope to see the enhancement at the soonest.
24 votes -
Sorting the device list by name
Sorting the device list by name
3 votes -
Unmerge Ticket Improvement
It needs to be possible to undo an accidental ticket merge properly. Currently, you can change the status of a ticket from Merged to Open/Pending to get it back, but it will be empty and the contents still on the ticket which it was incorrectly merged into.
This needs to have the original contents remain on the ticket and REMOVE those contents from the one they were merged into - they presumably haven't been sent to the contact who had the original ticket so it's not destroying a "paper trail" but deleting the contents from the original ticket which got merged IS.It needs to be possible to undo an accidental ticket merge properly. Currently, you can change the status of a ticket from Merged to Open/Pending to get it back, but it will be empty and the contents still on the ticket which it was incorrectly merged into.
This needs to have the original contents remain on the ticket and REMOVE those contents from the one they were merged into - they presumably haven't been sent to the contact who had the original ticket so it's not destroying a "paper trail" but deleting the contents from the original ticket which got…3 votes -
Ability to view KB attachments.
Ability to view KB attachments. Right now, we need to download it to see it. So, when the guys are on the field, they don’t need to download it. It would make it easier.
3 votes -
portuguese
Do you plan on having Portuguese available? Can we help?
1 vote -
fusion
fusionner un ticket dans un ticket programmer
1 vote -
Allow agent to be installed silently via Intune
Pretty straightforward. Allow the Atera agent to be installed silently via Intune, like it could previously. The agent can be installed silently via GPO on a domain, and Intune / Azure AD is just the next iteration of that.
4 votes -
Assign multiple technicians to a ticket
By a community member:
We need the ability to assign multiple technicians to a ticket. We have ceveral tickets that would consider projects requiring multiple technicians to coordinate assigned tickets.383 votesHey all,
We're excited to announce that we're exploring the development of a new feature focused on ticket queues and assigning technician groups in Atera.
Your feedback will be invaluable as we shape this feature to meet your needs and preferences.
If you'd like to provide input on this feature, please schedule some time for a call using the link below:
Your insights and suggestions are essential to us as we continue to improve and innovate within Atera.
All the best,
Yakov
-
We can actually upload MSIs and MSTs in a script
We can actually upload MSIs and MSTs in a script
4 votes -
Consolidate Reports & Report Cosmetics
We want to easily provide clients with a single report giving them a full overview of their environment
Thus being able to consolidate reports such as
Periodic Report with the Timesheet & Patch summary report, being in a position where you can provide clients with a single overview showing them - Overview, Patch Status, Ticket Status, Ticket Ratings.COSMETICS
We would like to be able to have a "Cover Page" on our reports
Further to this we would like to be able to add a description for the various sections eg. Tickets Rated "This is the feedback received from your team during the last month."We want to easily provide clients with a single report giving them a full overview of their environment
Thus being able to consolidate reports such as
Periodic Report with the Timesheet & Patch summary report, being in a position where you can provide clients with a single overview showing them - Overview, Patch Status, Ticket Status, Ticket Ratings.COSMETICS
We would like to be able to have a "Cover Page" on our reports
Further to this we would like to be able to add a description for the various sections eg. Tickets Rated "This is the feedback received from your…6 votes -
Ability to CC someone when you create a ticket
I would love to be able to add a CC on the new ticket page. I have to create a ticket , open it, have to respond to the ticket and add all the CC people 2 step process. If i could just throw a CC field just on a new ticket creation, that'd be helpful.
33 votes -
AzureAD Integration for Network Discovery
Integrate AzureAd to be able to Deploy Agents to Cloud-Only Devices without onprem AD
7 votes -
Ability to remove some columns and information from classic reports
Ability to remove some columns and information from classic reports
4 votes -
Section to enter and manage my vendors. For example, the name of partner, support contract info, contact information, etc.
Section to hold the information about my partners and vendors. For example, the name, address, contract information, contact information, costs of subscription maintenance and alerts before the contracts expire.
3 votes
- Don't see your idea?