I've started to look at Azure DevOps. I am personally the Jira product manager, and what I'm trying to do is have some sort of comparison. It all became very sudden. I was recently asked if, by the end of the week, I could provide a recommendation as to when one team should use Azure DevOps versus when one team should use Jira. I was told to look into why we should use one over the other or if they are so similar that it doesn't matter and we could just get rid of Jira. I've done very little research so far,

Obviously, Microsoft and Atlassian are competitors. Back when Azure DevOps was TFS, it wasn't even a close comparison in terms of boards. Jira blew TFS out of the water. It wasn't even remotely close. Well, then they obviously knew that they needed to improve and they basically made freaking boards look like Jira's boards and made some improvements on top of it in some ways. I suspect that there may be some underlying limitations with DevOps. I know that in Jira you could allow teams to just create the workflows that they want within reason, of course, while pulling from a series of predefined statuses and these things. Whereas, I don't know that you can do that in Azure DevOps. But then again, I don't know that it's necessary since you can already create the boards the way you want to.

I know that some people so far from customer feedback, tend to like the dashboards more in Azure DevOps. They seem to like the reporting options. They find it easier and more intuitive to use, however, I don't really know anything more about it than that. I just need to really know the pros and cons of each of these things. Here's what's surprising to me, if I'm at Atlassian or if I'm Azure DevOps or Microsoft, you would think that they would have something like that. You would think they'd be going, "Who is my biggest competitor? Well, I need to know these things so that I can improve my product and compete with him." However, when I reach out to them, I don't have any real comparison to work off of.

I did find one article online that was written by Atlassian and Azure DevOps versus Jira, however, it wasn't well-written.

View full review »

I tried Asana and Trello. I chose Jira because it integrates with many other applications and easily expands with its own apps. The integration within the Jira, Confluence, and Atlassian products is automatic. We don't have to spend time linking information and data. We just need to install it, and it will be ready to go.

View full review »

Compared with Jira, I feel Microsoft ActiveX Data Objects (ADO) is coming up pretty fast in the market since the features attached to the paid version work well. Microsoft ActiveX Data Objects (ADO) can easily integrate with other Microsoft products without needing any customization. Microsoft ActiveX Data Objects (ADO) is growing pretty fast in the market.

View full review »

We looked for an alternative since Jira’s licensing is expensive. We tested five to six other products. However, we chose Jira because it is quite a solid product. We had a lot of data to migrate and didn't want to spend too much time doing that.

View full review »

We are considering switching to DevOps and are currently carrying out an evaluation. The main reason is that our offshore team uses DevOps for everything. We started with Jira so they had to use it for us, but we're hearing that DevOps is better integrated with source control and releases, so it's something we're considering now. 

I've had a look at the pricing of DevOps and it's really strange. Basic pricing is $6 per user per month or if you want to include test plans it jumps to $52 per user per month, which is an astronomical jump. I'm not sure whether it's $52 for every single user on the system. Jira charges $7 per user, per month for the basic version or $14 per user, per month for the premium one.

View full review »

I have used some other test management tools, such as ALM. If it is a full model, it'll be too difficult to manage in Jira, but for Azure projects, Jira is the best. It depends also on the needs of the project.

View full review »

I was able to evaluate Micro Focus ALM.

View full review »

We went right away to JIRA without evaluating other options.

View full review »

As indicated above, we used Microsoft TFS. We tried to have a JavaScript team use TFS, but it didn't really fit into all the other ALM tools a JavaScript developer uses, so we quickly scrapped TFS and moved back to JIRA. The same was true for a .NET team; tried to have them use JIRA, but it was difficult to break the Microsoft eco-system. Not impossible in that case, just a culture shift you want to address carefully.

View full review »

Some of my teams have been using Version 1 and Rally. Because of that, I have been exposed to those tools for some extent.

My experience is much more with Jira. That's why I tend to go for Jira, but we haven't used many other solutions. Based on teams and what the people are saying, they find Jira to be more user-friendly. For Scaled Agile, I have also heard that they have found certain features in Rally more useful. But I don't know, I haven't used Rally to that extent.

View full review »

As far as I know, no other solutions have been considered as we've been pretty satisfied with this tool. 

View full review »

We currently are evaluating other options and are doing a study to see if we are going to continue using JIRA or move to something else.

View full review »

We evaluated Microsoft TFS and Targetprocess. Neither had a Portfolio planning feature, which is why we decided to stick with JIRA.

View full review »

We evaluated Asana and even Trello, as we were trying to simplify. But those solutions, among others, were too simple.

View full review »

Yes, TeamCollab, Home grown tools, Redmine, Jenkins, XLDeploy, Jazz/BuildForge and RTC. RTC and XLDeploy/Jenkins combo is still widely used and seen as an internal competitor.

View full review »

We tested three or four other options including, BaseCamp, Footprints, Drupal, and a lite version of BMC. We were a small area at the time and JIRA's combination of cost model and function won. View full review »

Bugzilla and other bug tracking tools were on the docket. We ultimately chose JIRA because of its UI polish and wide range of configuration options. When JIRA added Greenhopper, now JIRA Agile, that made the choice very simple going forward.

View full review »

We most probably didn't evaluate other solutions. For Portfolio for Jira, we considered other solutions such as Planview or ServiceNow, but for the software engineering development life cycle, we probably didn't evaluate anything.

View full review »

We chose JIRA/Confluence as they were solutions we can get up and running quickest, and also cheap.

View full review »

I did some research for a school project. I needed to compare it to Splunk and a few other tools. As a result, I'm not particularly interested in purchasing them.

View full review »

We are currently in the initial stages of contemplating a switch from Jira. 

View full review »

I have heard of many other solutions, such as Rally, but I have not explored it or compared it with Jira.

View full review »

Yes, we have other vendors and tools – evaluation is ongoing.

View full review »

I did not compare Jira to other solutions.

View full review »

To be quite honest, at the end of the day, a tool is just a tool. For me personally, it's hard to say this tool is much better than the other. From just what I know so far, Micro Focus Octane looks a bit more modern. But I don't know which Jira version we're using at the moment. Octane looks a bit more integrated, it looks a bit newer, but would I buy a tool because of that? Certainly not.

View full review »

I have tried or tested other options such as Excel, Monday, Trello, Tetra. In comparison, for how I use it, Jira is the most adequate for my daily job.

View full review »

I have been researching the difference between Jira and TFS, to decide what is better for our team to use. I'm very familiar with Jira. However, some of my team members have experience with TFS. I'm trying to decide which management tool we will use in an upcoming project.

I have found that, with TFS, a lot of the features are built-in, however, with Jira, you are required to add in plugins. 

View full review »

We did not evaluate other options before implementing Jira.

View full review »

HP QTP, Serena Business Manager, Rally

View full review »

We are a heavy user of the Atlassian tools and are a reseller. We do VAR work for other competing ALM solutions as well, notably Microsoft, IBM, HP, Perforce, etc. This is just the toolset we have grown into.

View full review »

Prior to Jira, we were evaluating Microsoft tools, but I don't recall the name. Possibly Microsoft Task.

We were evaluating Microsoft products for the same purpose.

The decision is a collective team decision. It may have been that Jira is easier to implement across the company.

View full review »

We tried Microsoft, but it only supports task management. It doesn't support creating test sessions the way we like to them. Also, it doesn't support product definition the way JIRA supports us and Microsoft's general interface is a whole mess, so we prefer JIRA.

View full review »

We looked at numerous other products. Some were more well-traveled offerings like Rally, AtTask, Clarizen, and Basecamp. Others were newer to the game like 10,000ft. View full review »

We evaluated other solutions before choosing Jira. We chose Jira because it is widely used.

View full review »

I used many other solutions, but the most popular I used was RedMine, Lotus Notes, TaskFreak, and Bugzilla. View full review »

It was solely based on requirement and preference of business stakeholders.

Some areas of business require to run licensed and proprietary software applications whereas some can have the opportunity to leverage open or closed source software. 

View full review »

We did not evaluate other products before choosing this solution.

View full review »

We did not look at any other complete suites of tools. We evaluated Rally Enterprise and VersionOne for project/defect tracking. Both of those options had decent levels of integration with our CI tools. Ultimately the value that the Atlassian suite gave us as a total package of discrete, but connected, components was above and beyond the piecemeal approach we would have had to take otherwise.

View full review »

We aren't looking for another solution at this time. We're happy with Jira. 

View full review »

I looked at other options, however, Jira is so famous and well known that I did not have to look for other software.

View full review »

We are currently using Jira but want to move the help desk to SharePoint. 

We have a Microsoft environment. SharePoint HelpDesk would fit better into our environment. As we are larger than we originally started, we have to make some changes to our current setup.

I also find Plumsail HelpDesk quite interesting.

View full review »

Before choosing this solution we evaluated SmartShift for work management, and we also tried Trello.

View full review »

We did not evaluate other solutions.

View full review »

I looked at Trac, Bugzilla, Test Track.

View full review »

No, did not evaluate other options, as JIRA fulfilled our need. View full review »

Yes, other defect management tools available on the market when I first evaluated JIRA 6 years ago.

UI of this tool is good.

View full review »

We looked at RedMine (open source), but features were limited, and it is not very user friendly. Other options such as BaseCamp and Asana were not really comparable products, in my mind, even though they come up on many comparison websites.

View full review »

• Quality Center
• Mantis

View full review »

We didn't evaluate other products.

View full review »

I am currently in the process of searching for better help desk management solutions.

View full review »

We did not really evaluate anything else. All of the other products were way too expensive for our purposes. Also, JIRA is the de facto standard.

View full review »

We started here with this product, after the decision was made.

View full review »

We looked at Micro Focus ALM vs JIRA, but it was quite expensive in comparison.

View full review »

No

View full review »

Not my area of responsibility.

View full review »

JIRA was the solution we used throughout. It had no competition.

View full review »

I've tried some other solutions including Plenty, ClickUp and Azure. I feel that Jira is far better than these other solutions. 

View full review »

I evaluated other options. I choose Jira to work with because it is a popular solution and many of our customers use it.

View full review »