Settings and activity
12 results found
-
30 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Rob Riccio
supported this idea
·
-
75 votesRob Riccio
supported this idea
·
-
1,224 votes
An error occurred while saving the comment Rob Riccio
supported this idea
·
-
10 votes
An error occurred while saving the comment Rob Riccio
commented
Looks pretty similar to request Ticket options and a couple others, but this description looks the most comprehensive. The existing priority, impact, and type choices are pretty limiting.
https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/44051331-ticket-options
Rob Riccio
supported this idea
·
-
34 votesRob Riccio
supported this idea
·
-
16 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Rob Riccio
supported this idea
·
-
11 votesRob Riccio
supported this idea
·
-
35 votes
Hey all,
We're considering the development of this feature in the coming months and would love to hear how you'd like to see workflows implemented in Atera.
If you'd like to discuss your needs, please schedule some time for a call here:
https://yakov-atera.youcanbook.me/
All the best,
Yakov
An error occurred while saving the comment Rob Riccio
commented
Really, the ability to send a message to anyone other than the requester, without having to change the requester, would be a big step up. Currently the 'to' field is just always the requester and cannot be edited or removed.
It is pretty standard to have external tech vendors these days for certain services and applications, and also pretty unusual that folks would want end users copied on those communications.
Rob Riccio
supported this idea
·
-
31 votes
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Rob Riccio
supported this idea
·
-
17 votes
Nice! The feature you requested is being considered for development. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
Rob Riccio
supported this idea
·
-
822 votes
Hey all,
We're currently designing an integration of Microsoft Teams with Atera.
We'd love to hear what are your expectations from such an integration.
Please answer this 1-minute survey if you'd like to provide your feedback.
Looking forward to hearing your thoughts.
Thank you,
Yakov Gorbulsky | Product Manager
An error occurred while saving the comment Rob Riccio
commented
Slack & GChat. SMS would be nice to have. A true integration with the ability to create tickets by sending a message to a particular profile, or create a ticket from an existing chat message / thread, add a comment / thread to existing ticket, send replies back to the user / channel / room / space and update statuses and other ticket data from within the Slack / Chat interface...or visa versa to choose Slack/Chat users/channels etc. from within Atera tickets and send related communications while capturing the thread in the ticket...Truly would add functionality and value.
Rob Riccio
supported this idea
·
-
1,542 votesRob Riccio
supported this idea
·
This could be implemented by expanding the Knowledgebase functions that are already present, but targeted at IT visible only documentation for e.g. password, token, and config info related to specific software, clients, and users. Why not keep the relevant info in Atera where we are managing tickets and devices?