Skip to content

Ideas and Feedback

Ideas and Feedback

Categories

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

4766 results found

  1. 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)
  2. 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)
  3. 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)
  4. 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)
  5. 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

    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)
  6. 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

    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  ·  Devices  ·  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. Implement domain-based restrictions for automatic contact creation from incoming ticket emails.
    Currently, the setting applies to either all or none.

    For example:
    - Do not create contacts for emails originating from public domains (e.g., Gmail).
    - Automatically create contacts for emails from recognized company domains.

    Ideas for configuation either:

    • Maintaining an allow list of approved domains, or
    • Maintaining a block list of domains to exclude from contact creation.

    Thank you for your consideration

    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)
  8. Since "Closed" status permanently closes a ticket without giving the requester the ability to re-open it, I'd like the ability to remove the "Closed" status from the Status dropdown box.

    The workflow we want to have is a technician sets a ticket to "Resolved" and then an Atera rule automatically changes Resolved tickets to Closed after a period of time which can be done. However technicians are accidentally setting tickets to "Closed" and duplicate tickets are being created when a requestor immediately replies.

    I know there's an option to allow "Closed" tickets to be re-opened, however I do not want…

    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)
  9. We name our devices in Atera based on Site and User. However, the devices themselves are named by their asset tag. When I search in Atera under Devices in EITHER category by device name it does not find it and the name is clearly in the information Atera gathers about the device. This is frustrating - please fix.

    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  ·  Devices  ·  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. It's super easy to schedule a report on any Patch Management and IT Automation profile and get an email every day.

    It would be soooo much more convenient and time-saving if you could get the export report in PDF format instead of a link directing you to the reports section.

    Hope this can be added at some stage.

    Thanks
    Ronald

    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  ·  Reports  ·  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. Add the ability to add a column showing total time logged to a ticket directly from the main tickets page.

    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)
  12. Currently, Atera does not allow filtering tickets or views by blank or null values in date fields, including built-in ones like Follow-up Date or custom date fields.

    You cannot directly filter for tickets where the date is empty. There is no native functionality to filter by empty date fields or by today/tomorrow in custom date fields.

    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  ·  PSA Tools  ·  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. When viewing a device for a customer, there is no way to get back to customer devices. Going back goes to ALL devices. That's not funny for administer more devices of same customer.

    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  ·  Devices  ·  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. Ticket Sentiment column is not exposed in API. When running reports, I cant get sentiment column for reporting the negative sentiment tickets

    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)
  15. Merged tickets have no history of their ticket titles. The ticket activity on the destination ticket just says "Ticket #40346 merged into this ticket" for example.

    The conversation entries are preserved but often the ticket titles will have the crucial information for the issue and they are lost when the ticket is merged.

    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)
  16. I have disabled the File Transfer tab in the Atera console; however, it still appears to be visible and accessible to the technical team. For data security and compliance reasons, we need to ensure that no file transfer data is visible or accessible to technicians.

    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  ·  Other  ·  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. At present, contract remaining hours are only reduced once a ticket is marked as completed or resolved.

    This creates a planning and capacity issue for us managing multiple open tickets for the same customer. Time may already be actively logged against several tickets that are still in Pending or In Progress status, but the contract balance continues to show those hours as still available until closure.

    As a result, the remaining hours shown can be misleading for operational planning and resource allocation. In scenarios where several tickets are resolved at the same time, the contract can suddenly move into over-usage,…

    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  ·  Billing  ·  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. Currently no email notification is sent to a technician when they are mentioned in a Public note, this to me sounds like a simple request and is causing members of our team to miss ticket notes that they have been tagged in

    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. We would like the "Group" field on tickets to be visible on the Customer Portal view so our end users can see which team within our IT department is handling their ticket.

    This helps because each team has their own set of SLAs and standards they follow, so it helps set better expectations and understanding with our end users when they have this information available to them.

    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)
  20. We need non-admin users to be able to create Customers. We have custom roles created, and a lower level technician should be able to create a new customer, assign contacts and set them up. Deletion (or even better - archive, deactivate, or retire a customer) should certainly fall to an Admin role.

    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)
  • Don't see your idea?