The part of this software I use the most on a daily basis is project management. This includes the project request form, the scheduling of project tasks, notifications through the system to customers, stakeholders, and the dev team. Other areas around our campus use different software and it's clear the differences with IT using TeamDynamix and them not.

The only thing I can say about a part of the software that might need to be a little better is just onboarding for new employees who use the service. There are so many different applications and uses with this software that it can be a little overwhelming at first. I will say they have a great customer knowledge base that has an article for just about any issue you might come across.

It is mostly positive. It has been relatively quick and the ability to upload documentation and images is very nice. One thing that bugs me is that attachments open in new windows/tabs and I don't see an option to set how you'd like that to happen. It would be nice to have a document always open in a new window. It would also be great if I could set tickets to open in a new tab instead of new windows but I don't see that as an option either. The workflow overall is pretty good and writing reports is pretty powerful yet simple. The day-to-day ease of use could be improved though. Also, support for high-efficiency HEIC images would be great. JPEG and PNG are good but a lot of newer phones shoot in HEIC by default. It would also save some space with attachments.

The ease of entering most information is very nice. The fact that we can route things pretty efficiently is also quite nice because we can route things to another user or group/responsibility easily. Integration options are pretty good and the fact that it supports our Single sign-on method for increased security is a plus.

It isn't always as flexible as IT needs it to be. It is not possible to have a requestor and recipient which would be a great help. Many of our users have office managers or assistants that submit work orders/tickets on behalf of the user experiencing an issue or requesting a service. Having the ability to have a requestor and recipient specified in TDX would be awesome. We also don't have an easy way to split tickets as the system is currently implemented. For example, we often have users submit requests to have say five PCs set up but our workflow requires we have one ticket per device for proper tracking. This becomes a greater issue when users need equipment repaired. It may be a bit of a limitation of how we are implementing things but simply copying the work order requires we adjust multiple pieces of content or triggers a workflow for which users need re-approve tickets since there are charges for some services and not others. The ability to clone tickets with the approval status still in place would be a great option for situations where the requestor has already approved the charges for the work on the main ticket. I would also really like to see an option to require data fields at specific steps in the ticket workflow. Currently, this seems very limited. For instance we can require someone to enter their phone number and location but we can't require the technician fill out the solution or resolution method for the ticket when they are resolving/closing tickets.

Used for IT support at a higher education institution. Seems... fine. Less bells and whistles than ServiceNow but that's ok, we don't need them and they are generally overcomplicated. Simple is best, but there's some QoL improvements that will help it flow better.

Reports are powerful (if a little unintuitive) and the asset management system is good.

The software is constantly opening up new windows for every asset record or ticket that is opened. It's very frustrating and they easily get lost amid the other windows that I have open. Also, there is no dark mode, so it is very harsh on the eyes with no alternative scheme for those that would prefer it.

We rely heavily on the incident management. It has been a very stable platform and functions well for ticketing.

The user interface is relatively simple and easy to navigate. It has become more useful with the recent features that have been implemented.

Our implementation was back on version 9. The newer versions added more features, but in turn caused a lot of our initial methods of ticketing to become obsolete. Now we have a tremendous amount of "bloat" that needs to be cleaned up.

My job has completely transformed since the implementation of TeamDynamix in a positive way. We can understand our workload, see into the future with less uncertainty, and our users have a clear understanding of status.

Easy configuration was a key metric in selecting an ITSM and PPM product. We implemented the ITSM side in 2015 and found it incredibly easy to use, which made our transition to the PPM side in 2017 a no-brainer.

The company is a bit young and small so working with their integration tools and APIs at first was a bit difficult. They have greatly staffed up recently and their toolset has grown to our delight.