This is super important! As an IT department using Atera, having our projects in the same place as our tickets would be a game-changer. It would allow us to track all orders by project number seamlessly. Right now, we're juggling a separate board and then creating tickets every time we work on a project just to track time in Atera.

I believe in you all. Seriously. All I want for Christmas is a project management system... pretty please with debugging on top! 😄🎄

This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.

This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.

This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.

This is very important to us. At the moment we are having to use standard tickets for projects, but there are no stages for progress/sign-off, we cannot crate tickets/tasks that fall under larger projects, and using the standard tickets for projects (that often are open for long periods of time) is skewing our support metrics such as average ticket closure time, which is very frustrating.

This is HUGE or a Change Management section along with it like Fresh Service has

As the exisiting of an service catalogue is crucial for meeting the requirements of the ITIL framework I vote this up. We need the possibility to create service templates with free to define fields. This catalogue should be made available via the customer portal from my perspective. When the user requests a service an automated process with free to define timelines/SLAs should be starting. I support the idea of Nicos to manage this part completely apart from regular ticketing. Also there should be an option to define that access/request is only allowed for a specific group of indiviuals. If you want a direct input via videocall, feel free to contact me.

I third this! Is there any update to this?

Need to have a "Type" that can be used for long term projects that won't affect the ticket averages and can be viewed returned to as the project progresses.

Ability to have a section on Project management, track project stages

Atera needs to add a new module for Project Management. Have the ability to create a customer project, then assign tickets to the project and be able to the output that info to assigned technicians calendars (similar to tickets). Have a master Project Board that can be filtered by customer and produces a schedule and Gant Chart for tracking.

We love for you to add the CRM and Project Management tool to your platform. It would be much more helpful for us to be able to work on one platform rather than opening multiple applications just to get the work done. Hope to hear from you soon. Thank you!

I second this feature as i am in the procurement team and this is a process we mapped out vigorously, wishing there was an atera feature for this. We opted for ticket create using a different naming convention just so tech's and admin can differ the 2. It does at present make invoicing and reporting messy, so would love this feature independent of "work tickets".

In many occasions, the customer does not actually need to open a support ticket, but needs to request the provision of a specific service (i.e. the procurement and installation of a new PC). This is not considered a ticket and is not part of Incident or Problem Management. It would therefore be very helpful if a service catalogue could be established and the customer place service requests from within that catalogue, allowing for separate management from standard tickets.

Furthermore, if a basic Project functionality with progress tracking could be provided, where multiple resources could be allocated to specific tasks, that would be great.