"The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening."
"You can record your unit testing, regression testing, UATs, et cetera."
"With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board."
"The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence."
"Jira is a pretty capable product, and a lot of features are valuable. We value being able to set up separate projects and configure teams in them, set up sprints, and manage our sprints with its history tracking. These are all very useful features. It has been a very popular product for our work."
"One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily."
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"The level of stability is quite good."
"The initial setup is fairly easy."
"The most valuable feature is the backlog."
"I feel that the test plan and test tools are more manageable in TFS."
"The most valuable feature is simplicity."
"Basically, the capacity to construct various products is something I find handy."
"The interface is easy to navigate."
"The most valuable features are test case writing and bug tracking."
"The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."
"The next-generation software projects lack a lot, and I found quite a few bugs. There are some really basic things that you still cannot do. For instance, to put a mandatory due date for a task that you create in one of these projects is still not available. That's a bit of a block because people, especially those who are not technical, are not going to add anything if it's not mandatory. It's going to be difficult to teach them that they should do it anyway."
"This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning."
"We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface."
"It is not intuitive."
"The support could be improved."
"We'd like to see Jira have more integration with a development ID."
"The reporting needs to be better."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"The usability of TFS is not that great."
"The dashboard and the customization of dashboards is an area they have to work on."
"This solution is quite old and it is already being bundled as Azure DevOps Server."
"I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress."
"There should be management of the project built-in."
"The interface can be improved and made more user-friendly."
"The user interface could be improved to make it simpler and increase usability."
"I would like to see the reporting features expanded so that I can see details on the users connected to all of the projects."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 133 reviews while TFS is ranked 6th in Application Lifecycle Management (ALM) Suites with 17 reviews. Jira is rated 8.0, while TFS is rated 7.8. The top reviewer of Jira writes "Great for collaboration, very stable, and extracting data is straightforward". On the other hand, the top reviewer of TFS writes "Good traceability for managing workflows, but not flexible enough for agile environments". Jira is most compared with Microsoft Azure DevOps, Micro Focus ALM Octane, IBM Rational DOORS, Rally Software and Micro Focus ALM Quality Center, whereas TFS is most compared with Microsoft Azure DevOps, Rally Software, Visual Studio Test Professional, Micro Focus ALM Quality Center and Zephyr Enterprise. See our Jira vs. TFS report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
