Settings and activity
62 results found
-
7 votes
An error occurred while saving the comment 
Danny Stergiadis
supported this idea
·
-
77 votes
An error occurred while saving the comment Danny Stergiadis
commented
I'd like to add to this. We assign tickets to developers but they dont have technician user. They are setup as a client and can see the tickets. However it's become difficult to manage our views and not see those dev tickets. How about a Technician with no license just for holding tickets that other techs dont want to see on their boards. No login allowed. We can just assign tickets to that tech and visually see them and move them to other techs.
Danny Stergiadis
supported this idea
·
-
14 votesDanny Stergiadis
supported this idea
·
-
98 votesDanny Stergiadis
supported this idea
·
-
67 votesDanny Stergiadis
supported this idea
·
-
32 votesDanny Stergiadis
supported this idea
·
-
29 votesDanny Stergiadis
supported this idea
·
-
9 votesDanny Stergiadis
supported this idea
·
-
6 votes
An error occurred while saving the comment Danny Stergiadis
commented
We use the API to pull tickets details, time and other fields to create invoices in QBO. But we can't pull products added to any ticket through the API as this doesnt exist as a function. Some background: When a customer orders new computers (or any hardware) we save the product details of those computers and the labour/time to setup, etc into the ticket. Right now we have to flag the ticket with a custom field in order to ensure someone visits the imported QBO Invoice and adds the products manually. This is very time consuming. Having an API to access the products by ticketID is very important.
Danny Stergiadis
supported this idea
·
-
29 votes
Hi,
Great news! Your idea has been approved and is planned for implementation, however this will require a longer duration than Q3 '25.
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 - API endpoint - get asset.
Best regards,
The Atera Team
Danny Stergiadis
supported this idea
·
-
7 votesDanny Stergiadis
supported this idea
·
-
15 votesDanny Stergiadis
supported this idea
·
-
2 votesDanny Stergiadis
shared this idea
·
-
4 votesDanny Stergiadis
shared this idea
·
-
29 votesDanny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
6 votes
An error occurred while saving the comment Danny Stergiadis
commented
Further to this, data should be linked to the customer not the contact. Currently tickets are directly related to contact, and contact is related to customer. When you delete a contact who was fired at customer location all tickets and underlying data are deleted. This should not happen. Employees come and go...we are not billing that employee or have to answer to them. We answer to management at our customer. This needs to change.
Danny Stergiadis
supported this idea
·
-
20 votesDanny Stergiadis
supported this idea
·
-
44 votesDanny Stergiadis
supported this idea
·
Request:
Add to automation "Actions" so that we can pick Action Type "Set FIeld Value" and then pick "Related Field" = Customer and then "Value" being a drop down of Customer names.
This way we can build automations to put tickets under the right customer based on Ticket Title.
Why?
1. Clients sometimes send us emails directly instead of sending to the email we have setup in Atera to generate tickets. So we have to forward their email to create a ticket, but sometimes their email is not in the contacts of their customer settings and we have to manually go in after the ticket is created to fix which customer the ticket is assigned to.
2.We also have automations running in other server farms and systems that we receive emails from. These emails have our client's account numbers or names in the subject. We want to automatically assign these to the right customer based on ticket title when the ticket is being created.