4772 results found
-
Ticket body - not wrapping text properly words cut off
Finding clients that type a longer ticket description the ticket body is not wrapping and several words on the right are cut off.
1 vote -
US pacific time zone support.
There always seems to be a day delay in regards to ticket responses. I think ticket would be resolved twice as fast if there were a dialog closer to real time.
Thank You.
1 vote -
Inactivate User based off of Entra ID Sync
Atera's existing Entra ID integration is a one-way sync that creates new users and updates existing ones. On each run it imports users found in Entra ID and refreshes a set of profile fields (name, job title, phone, and mobile) on records it matches by email address.
However, it does not sync a user's account status, and it has no deprovisioning step. A user who is disabled or removed from Entra ID the sync leaves their Atera record in place and active. This obviously causes a data consistency issue as users are now showing active in Atera that have been…
1 vote -
Allow scheduling of child tickets
When creating a child ticket allow it to be scheduled, aids in project management and disable/enable scenarios for sharing, access or user leave.
1 vote -
Resize comment box
Ability to resize the comment box, not just full screen
1 vote -
Linklist last visits computers, etc., in the left-hand menu
It would be very helpful to have a list of links to recently visited customers, computers, etc., in the left-hand menu bar. Otherwise, you end up clicking yourself to death. That should be easy to do.
1 vote -
Allow ticket properties to be made visible based on the ticket Technician Group
Atera currently displays certain custom fileds based on the ticket form that's selected.
This requires us to create Tickets Forms e.g. Workforce tickets that aren't user facing so that we can see the corrosponding fields inside a ticket (See attached screenshots)
Because we have to use a form for displaying these fields, a non user facing form is displayed in our user ticket form which isn't ideal.
We use technician groups to act as different queues for different types of tickets e.g. Workforce tickets. Can we make certain custom fields visible based on the Technician Group rather than having to…
1 vote -
Feature Request: Repeating Alerts for Critical Devices and Scripts
Hi Atera Team,
I'd like to request the ability to configure repeating alerts for designated critical devices and scripts.
Current Problem
Currently, Atera sends a single notification when a device or script enters a failed state.
In many environments, that single email can easily get lost among other monitoring alerts or simply among the hundreds of other emails people receive throughout the day. As a result, the customer may never see the notification until much later, allowing a critical issue to go unresolved for hours or even days.
Proposed Feature
Allow any supported object to be marked for repeating notifications.
…
1 vote -
Feature Request: Per-Device Alert Delay (Only Alert if Offline for X Minutes)
Feature Request: Per-Device Alert Delay (Only Alert if Offline for X Minutes)
Hi Atera Team,
I'd like to request a feature that would significantly improve monitoring for environments with devices that experience brief or intermittent connectivity issues.
Use Case :
Many of my customers have surveillance systems that consist of:
A Camera Server (Windows PC)
Multiple Generic Devices representing IP cameras on the customer's networkSome cameras may briefly disconnect dozens or even hundreds of times per day due to aging network cabling, camera hardware issues, or temporary network instability.
Current Problem :
Atera generates an alert every time one…
1 vote -
Ticket Times
If a user raises a ticket, and has a device linked to that user. When you connect to that device via Atera, it should automatically add the time you were connected to the ticket. Other tools such as Autotask have this feature and it is extremely useful
1 vote -
ticket time
If a user raises a ticket, and has a device linked to that user. When you connect to that device via Atera, it should automatically add the time you were connected to the ticket. Other tools such as Autotask have this feature and it is extremely useful
1 vote -
1 vote
-
when resorting cols in the ticket they need to stay how i set them
The new ui for tickets doesn't fit on a single screen and the order they put the data cols in is useless (who cares about sentiment its a joke) when I reorder or remove COLS from the ticket screen the changes should persist instead of resetting every time page reloads. I need to have it so statuses of the ticket are FIRST .
3 votes -
Link Asset Inventory status to the Devices tab — they should be the same record
What I'm asking for: Surface asset status directly on the Devices tab — either as a column or inline on the device record — so I can see at a glance whether a device is Retired, In Stock, or In Use without leaving the tab. Even better, link the Asset record to the Device agent so they're the same object, not two parallel lists.
2 votes -
Dynamic field mapping for Cloud Actions via Custom Fields
Summary
Cloud Actions should be able to pull values for API calls dynamically from user-defined Custom Fields, instead of only supporting static input or full list retrieval. This would enable targeted update/write operations against the Atera API (and external APIs) without having to manually identify the relevant record.
Current behavior
When I set up a Cloud Action against the Atera API (e.g. "Update Customer"), I can essentially only retrieve all entries via the API. There is no way to dynamically bind a call's parameter to a specific record or an existing Custom Field. As a result, targeted updates are cumbersome…1 vote -
Time Since Last Activity Condition
I would like to see a trigger or condition based on the Time Since Last Activity of a ticket.
I am wanting to create an automation rule that sends an email to a technician after 72 hours since last activity on an open or pending ticket as a reminder to follow up on the ticket.
1 vote -
Ability to Edit
Often we receive out of office replies, large signatures, or extraneous information (like a giant forwarded email string) in tickets. Sometimes, because of how Atera is designed, we put the wrong info in a ticket. We have to have the ability to clean this up. Even if it's an option we can click in Admin we need that option.
It's at the point where I'm ready to look for another helpdesk application.
5 votes -
Limit bearer token to ipv6 address
Allow IPv6 as well as IPv4 on bearer token.
When creating a new API Token I have to allow all Any since our production servers use IPv6 and the input form will not allow that.
1 vote -
Status Selection on Ticket Creation (Dashboard)
Feature Request
Add a Status dropdown field to the ticket creation form in the Atera RMM dashboard, allowing the technician to set an initial status at the time of ticket creation rather than defaulting all new tickets to "Open."Current Behavior
All tickets created from the dashboard default to "Open" regardless of context. There is no way to set the status during creation — it must be changed as a second step after the ticket is saved.Requested Behavior
When creating a ticket from the dashboard, the technician should be able to select a status from a dropdown at creation…2 votes -
Device Page Title Arrangement
On the Device page you should improve navigation by organizing the title line in this format:
Back arrow, Device OS Type, Favorite Star, Customer Name, Folder, Device name
Also in the sub title you could list the currently logged in or last active user next to the contact to see them at a glance instead of navigating to the tabs below.
This would prevent the need to look at the Overview tab to identify the relationship of the device. it is exspecially helpfull if multiple organizations have similar or exact device names (ie:server). Also providing a refresh button or auto…
1 vote
- Don't see your idea?