782 results found
-
UI Ticket page. My feedback as on reddit.
See my post on Reddit for mock up picture.
/r/atera/comments/1l8qivn/uilikeimachildsidebarandtickets_page/Ticket’s page.
Remove duplication. Text or Icon. PICK ONE!
Contrast on objects. Make things stand out.
Resizing, things should be adjustable. (so we can see useful info.)
Dead space, so much is wasted.
Colour, even colour-blind people can see at least two colours and bits in between.
BAN GRAY! If it’s a primary action make it black or a high contract colour.
Columns would be nice if we could select / make our own page. (we can dream)1 vote -
Ticket type match custom forms
I have created custom forms, e.g. “incident, request, change, onboarding, etc.” would like the custom form to be able to automatically link to a ticket type. For example when a “change” type ticket is chosen, the custom form I made for Change tickets is automatically selected and can’t be changed by the requestor creating the ticket. This way the correct form with the correct-custom fields is used. I am trying to move away from from creating tickets by email and using the portal and this feature would help with getting the required information for a particular ticket type. Also help…
3 votes -
email non delivery report
We have had several issues where clients do not receive ticket replies as Atera's mail server has blocked them. In this instance we need to be notified of the block from Atera's mail server and suggest this be implemented using a NDR or other notification back to a nominated email address.
23 votes -
Quick access to tickets to show status (awaiting technician response etc)
Quick access to tickets tabs to show their status on top navigation bar (e.g., awaiting technician response, etc.)
The newly implemented feature to highlight ticket status with colours, allowing us to easily identify and act on tickets awaiting responses.
I would love to see this feature applied throughout Atera, not just on the tickets page.
1 vote -
Ticket Forms - Description -
We would like to be able to create Ticket Templates where you can pre-fill the description area. So (just like with quick reply templates) you can make tickets for standardized situations like callbacks, repair requests etc. As an example if you can create this you'd select the Callback template and the Description area will be filled with:
Issue
Contact info
Phone number
Avaible to be called back between xx am - xx pmI realise that some of the info above is also available in a ticket, but the above is just an example.
2 votes -
Assign tickets to specific clients based on the subject line
Set up an automation rule to assign tickets with a specific subject line to a designated client.
6 votes -
Ticket queues / Technician groups
Hello Atera Community,
I'd like to propose a feature that could significantly enhance our ticketing system: dedicated ticket queues with the capability to assign tickets directly to these queues.
Why Ticket Queues?
Ticket queues would allow us to categorize and prioritize incoming requests more efficiently, ensuring that each ticket reaches the right team swiftly. This could dramatically improve our response times and service quality.
Assigning Tickets to Queues
Imagine being able to route tickets to a specific queue with one click; just assign the queue just like you do contacts. However, make the queue a contact as well. So we…
56 votesHey all,
After speaking to many of you and designing this one together, I'm happy to announce we are now beta-testing a new feature focused around technician groups/ ticket queues
The new module allows:
- Creating technician groups for better team organization
- Assigning tickets to groups for efficient workflow
- Filtering and creating custom ticket queues to manage priorities in the tickets list
- New ticket automation rules improvement with new triggers, conditions, and actions
Some use cases for this new feature are:
- Auto-assigning tickets to queues based on conditions
- Notifying admins on escalations
- Round-robin ticket distribution between group members
We hope to finish beta testing and release the feature to all customers soon, we'll be sure to update you once that happens!
Yakov
-
DateTime or just Time custom field
Currently, there is only a "date"-type custom field. We have need for tickets that also include a start and end time as well. It would be nice to have a time field, and/or a combined date/time field.
1 vote -
Inside the e-mail templates for ticket, add a "Time Spent" snippet
If that snippet "Time Spent" would exist, you can automatically sent an e-mail to the person inside your organization with the "Total Time Spent", the moment an IT-engineer flags a ticket as resolved.
That person can immediately start with the invoice, instead of first logging on to Atera, generate a report or open the actual resolved ticket to find out what time the IT-engineer spent, solving the ticket.
This would save time for the person who needs to invoice all resolved tickets.3 votes -
Add to ticket automations
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?
- 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…
1 vote -
The ability to forward from a ticket inside the ticketing software is a must.
Quite simply, add the ability to forward a ticket to someone outside of the ticketing system so they can add a comment to the ticket or just simply see what the ticket information is.
Having to screenshot or copy paste a ticket contents into an email client and send to an external party is a little backwards. Being able to connect directly to a 365 mailbox with OAuth would be nice also.
1 vote -
Color coding options for different ticket status
Color coding options for ticket status's.
12 votes -
Save Public Reply Without Emailing
It would be nice to have an option to save a "Public reply" to a ticket without initiating an email to the contact, this way the notes are visible to the Client contact in the customer portal but we don't have to necessary spam the contact with technical notes via email.
3 votes -
scheduled ticket frequency monthly at specific weekday
It's not smart to set a ticket frequency to a numbered day, because that are changing weekdays.
A schedule like "first tuesday", "second wednesday" or "last friday" would be much more important
1 vote -
Time Based ticketing rules based on ticket Activity Status (NOT Ticket Status)
Exactly as it says... Allow ticket automation rule to be triggered by ticket activity status (which is an automatically updated field), not just ticket status (which is manual and can be forgotten).
Use case - if ticket is waiting for customer reply for 24 hours, send reminder email. If ticket is awaiting technician reply for x hours, send email to rep and change priority.
7 votes -
Ability to add time to internal notes
I would like to see the internal notes have a place to add time. I work my tickets through internal and external notes. I should be able to add my time right to the notes. Having the time entries with separate notes in a separate section causes me to have to double enter.
You could then remove the time entry screen. It is not efficient to have to click the ticket, click the time entry, then click on each note to see what it says... but it has to be there to pull to the timesheet.
At the very least,…
2 votes -
planner
I would appriciate a lot to have the possibility to organize my tickets in kanban mode, as I could do it in Microsoft Planner. I could drag-drop tickets in columns : backlog, planned, in progress, ended ...
Actually i use categories but it's not as good as Planner.
Thanks for your attention.3 votes -
Scheduled ticket for users
It would be great if users could create scheduled tickets themselves.
For example: "I'm going on vacation, and when I return, we’ll need to handle this specific topic together" or "A user will be leaving the company on a specific future date."Currently, we have to create these tickets for them, which is time-consuming.
Also, when we do it, users don’t see the ticket in their own list, so it’s hard for them to know whether a task has actually been scheduled or not.1 vote -
Add custom "Types" to use for tickets
It is quite limited to only have 4 "types" to choose from.
Incident
Problem
Request
ChangeSometimes we get tickets that are neither and would like to add our own custom types to help better categorize the tickets that come in.
8 votes -
Ability to filter when you search
When you search and it pulls up tickets, there is no way to filter these further. Since we can't filter by status to only show open tickets, we have to scroll through a long list of ticket search results to find ones that are open.
4 votes
- Don't see your idea?