Settings and activity
33 results found
-
382 votes
An error occurred while saving the comment
Alex Noce
supported this idea
·
-
321 votes
Hi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
An error occurred while saving the comment
Alex Noce
commented
You must consider this more seriously... we have a major gap in our device tracking. We should be able to generate a report of all decommissioned hardware should our clients ever require this information. This has happened to us in the past, and we thankfully kept a spreadsheet tracking basic computer information and serial numbers for an auditable report.
Please also consider that when the Atera agent is uninstalled from a device, whether intentionally or by accident, these should be identifiable for reinstallation or archival. Not all devices are physically recycled when we need to remove them from our active management.
In that regard, when an agent is reinstalled, Atera creates a DUPLICATE instead of attaching to the existing device record... this obliterates all hope of device history... absolutely unacceptable, this must be addressed immediately.
Alex Noce
supported this idea
·
-
8 votes
Alex Noce
supported this idea
·
-
49 votes
An error occurred while saving the comment
Alex Noce
commented
An error occurred while saving the comment
Alex Noce
commented
I personally would love to see Subfolders AND Tags as entirely separate feature... We like organization, and a bunch of disjointed folders to not facilitate a hierarchy of folders which more accurately represent the reality of devices we support.
I would like to see subfolders, folder sorting, and global folders (basically folder templates that exist for all clients by default).
In addition to these obvious changes to folders, tags is a great idea - something a bit more powerful than custom fields that cannot be changed in bulk. Tags could honestly replace the idea behind global folders, as tags would naturally be something that fits across multiple customers as they are often just a single word to quickly categorize a large pool of objects.
Alex Noce
supported this idea
·
-
40 votes
Alex Noce
supported this idea
·
-
39 votes
Alex Noce
supported this idea
·
-
145 votes
Hi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
You can also follow this in our Pubic Roadmap.
Best regards,
The Atera Team
An error occurred while saving the comment
Alex Noce
commented
Greetings! I think you need to consider a many to many relationship between devices and contacts, here is a related idea: https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44832964-assign-multiple-contacts-for-a-single-device
Alex Noce
supported this idea
·
-
190 votes
Alex Noce
supported this idea
·
-
411 votes
Hi,
We wanted to let you know that your idea is currently under review by our product team.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
An error occurred while saving the comment
Alex Noce
commented
Dear Atera, please bring your attention to the glaring feature that should be a super quick implementation. Other ticketing systems consider this to be a 'watcher' rather than actually 'assigning' the ticket to multiple people. I'd honestly prefer that because we can always change the assignee to whomever is actively driving the ticket to completion.
Related ideas:
https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44963740-option-to-assign-multiple-contacts-to-a-ticket
https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44928382-multiple-contacts-for-a-single-ticket
Alex Noce
supported this idea
·
-
22 votes
An error occurred while saving the comment
Alex Noce
commented
Dear Atera, please bring your attention to the glaring feature that should be a super quick implementation. We constantly see requests from our users where multiple people are copied, they expect those people to also be included in future responses to the ticket. Not only should that happen, but we should also have the ability to add/remove people ourselves both to the ticket as a whole as well as any individual response (almost like it is an e-mail, yeah?).
Alex Noce
supported this idea
·
-
23 votes
An error occurred while saving the comment
Alex Noce
commented
Dear Atera, please bring your attention to the glaring feature that should be a super quick implementation. We constantly see requests from our users where multiple people are copied, they expect those people to also be included in future responses to the ticket. Not only should that happen, but we should also have the ability to add/remove people ourselves both to the ticket as a whole as well as any individual response (almost like it is an e-mail, yeah?).
Related ideas:
https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44963740-option-to-assign-multiple-contacts-to-a-ticket
https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44015103-assign-multiple-technicians-to-a-ticket
Alex Noce
supported this idea
·
-
22 votes
An error occurred while saving the comment
Alex Noce
commented
Everyone needs to open a ticket with support and send them a screenshot to these ideas. 4 years later this idea should be implemented, or we need a concrete reason for why it cannot be implemented.
Alex Noce
supported this idea
·
-
59 votes
An error occurred while saving the comment
Alex Noce
commented
Everyone needs to open a ticket with support and send them a screenshot to these ideas. 4 years later this idea should be implemented, or we need a concrete reason for why it cannot be implemented.
Alex Noce
supported this idea
·
One very specific scenario is a laptop missing or stolen, or even termination of remote employees.