The product must improve its stability. It must do more innovations. It could be made more efficient to provide the best responses. It will help us with internal and external processes.

The product should be priced better. 

The stability of the product could be better.

The tool's subscriptions are expensive for medium and small businesses. It works fine on Windows. However, it is not stable on other platforms. 

Improvement-wise, I would like customer support to be more friendly. The overall customer support needs to improve.

Sometimes it gets tough when you're dealing with a larger process if you're accessing it through the VPN. If you're not on the local network, you're accessing through the VPN, which already makes it slower in general, and then on top of that, if you're accessing a really large process, you're going to feel it slow down even more. The product sort of gets stuck when you're trying to connect and operate for the first time. 

When you go into the front-end, the web portal, if, for example, you pick up an issue, it would be ideal if the branch was automatically created in the repository. Right now, this isn't the case.

The user experience for the task assignment functionality, and more generally the software lifecycle development, needs to be improved. This includes assigning tasks, as well as reviewing those that are pending or ongoing. For example, Jira has an excellent user experience, and it should be more like that.

We would like to see better integration of documentation.

I would say compared to some more modern tools which are made to work offline, with this solution you have to be connected all of the time and with a central server. In our case, it's not a big problem because we all work on-premises, but it can be an issue if you have teams in different locations. Then you don't have synchronization. I would say it's the main problem - I would love to see a better way to work offline.

I think the new version allows you to choose to have different source control. But we use VPN, so we can bypass and still be connected to the company. So it's okay for us and we are on a very small scale, only ten users. So it's easy to manage.

Many important features that are useful for an organization but I feel that even if it is improved, some of the features are not necessary.

I know the tools. I train people here by using these tools. Today, the software development team and some engineers in production are going to be using the tool. Yet I feel it is necessary to involve more time and practice with the tool here in the company.

I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see.

I would like to see the inclusion of more programming languages, especially better support for Java.

Accessibility switches available on the desktop should also be available on mobile devices for coding or developing on the go. 

Technical support is a bit lagging so could be improved. 

It would be nice to see some of the authentications compacted to the solution which are done with Nudi.

Support response time could stand improvement.

The price could be better. 

We are looking forward to the new Blazer system that is coming out soon. It is currently in beta on the service side, so we are looking forward to the new version that will be on the client side too. I also would like to see an improvement in the technical support.