Skip to content

Ideas and Feedback

Ideas and Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

4781 results found

  1. The default ticket reply window size is not only fixed size but too small, can be difficult to scroll in - can we make it draggable to enlarge or at least 25-30% larger?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Customers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. When creating a new ticket, there should be a Cc option in order to add different emails.
    we have tickets that need approval from others and if the Cc option is there they could get straight away instead of going after and send another message to the Cc.
    thank you
    Barbara

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Helpdesk Agent  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Ability to resize the comment box, not just full screen

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  User Interface  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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 network

    Some 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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 .

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Asset management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IT Autopilot  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. It would be extremely useful if Atera offered a way to define dynamic device groups. These groups could be created based on:

    • Folder structures
    • Naming conventions (e.g., Notebook, Desktop, Server*)
    • Custom filters
    • Manually assigned devices

    Once defined, these groups could be used as target collections for various actions, including:

    • Script execution
    • Software deployment and removal
    • Patch management
    • Reporting and analytics
    • Other automation tasks

    This would allow administrators to perform recurring tasks across multiple customers, locations, or device types without having to repeatedly search for and select individual devices.

    Practical Example
    Today, I can use software reporting to identify…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tickets  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 239 240
  • Don't see your idea?