Jira Reviews

Getting our Service Desk out of a system of stored emails and into a ticket system where we can queue, assign, track, report, and store knowledge has been great for us.

JIRA was our first experience with ITSM implementation. It allowed us to reduce the amount of tools we were using, standardize our procedures, and measure our work. This allowed us to show the need for additional staff resources, additional training, track our busiest times and prepare for them.

Administration: JIRA administration is not as efficient as it should be. JIRA is aware of many relationships but doesn't bother to show them to you on the admin side. Example. JIRA knows what roles I'm using for a project because they are listed in the permission scheme. Rather than just showing me the roles listed in the scheme it will show you every role in the database. This makes the page load slowly and is frustrating to scroll through. There are many other examples of this same function for administrators.

31 months

No, deploying JIRA in our VM environment was not a problem.

We did have some issues with stability in the beginning. We were pushing the ticket limit is 4.1 and it caused some issues. We later tested the High Availability Clustering and the archival tools for this which were very nice and did work, but were to expensive at the time.

We did have some limitations but that was not an issue after 4.4 when the ticket limit was doubled.

Customer Service: Customer service has not been helpful but I have not minded since the wiki documentation and Atlassian Answers forum have been great. The developers I have done beta testing for have also been great. They are good about using your feedback as they design.Technical Support: The wiki and forums are wonderful. I get all my answers from those two sources. Talking to a customer representative has not led to anything useful.

We had a system called EPIC that we had created in house and did not have the functions and capabilities JIRA had. JIRA was also a more cost effective solution.

I did have complexities in the beginning and again as I was scaling but they were not the tool as much as establishing efficient shared processes and procedures.

In-house. Two of use spent time learning the tool and implementing it in our area first and then across the University.

In dollars, nothing. We are not charging to use our implementation. In employee resources, project planning, training, staffing, process efficiency, a lot. It would be hard to say the actual cost.

Our original cost was about $2000 for our licenses and hosting costs to get started. We are currently paying about $6000 dollars per year for our current installation.

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.

This is a very cost effective application if you are looking to do application development, incident management, request fulfillment, problem management, knowledge management, or project tracking at a low maturity.

Jira is used by my clients across their organizations. They use it for everything related to IT solutions.

Jira has been a good, powerful tool for collaborating across large groups of people.

I use structures as well as the reporting features, personally. The JQL feature is powerful and easy to use. 

The Jira dashboards could be more useful. The dashboards have good widgets but the comparison of data over time or extraction of trends from the data is not easy. This is important for us from a governance perspective. Currently, we do this outside of Jira in Excel manually or using other reporting tools. 

Secondly, it would be useful if the graphs in Jira could be more customizable. If you draw a graph on Excel sheet, you are able to do a lot of customizations. Those kinds of customizations are not possible with the current implementation of Jira. 

When you create structures such as hierarchy, including epics and stories, if you change something, the fields are not correlated. This makes the tracking of changes a manual process.

I have been using Jira for more than a year, but I'm working on a project which has been using it for five years.

This is a stable solution but it can be quite slow. The speed at which Jira operates depends on how it is implemented. 

I would rate this solution a seven out of ten. 

Public Cloud

We primarily use the solution as an ALM, an application lifecycle management tool. 

I like the entire workflow customization, which we could set up for our usage.

There are some really great in-built reports.

The solution is stable and reliable.

The scalability is great.

In terms of the initial setup, the solution is easy to implement. 

We've had zero issues with the product. It's been great.

Even though I like the reporting part, we have some issues. I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports. This is when in-between integration comes into the picture. There could be easier integration. It used to be easier in 2016.

We've been using the solution for more than three years now. It's been a while. 

The product is reliable in terms of performance. It's stable. There are no bugs or glitches. It doesn't crash or freeze.

The solution can scale well. If a company needs to expand it can do so. It's not a problem.

We have 250 or more users using the solution. We might go up to 300. It's not likely we would pass 400 users. We might increase the usage a little bit.

We've never had issues with Jira and therefore have never reached out to technical support. I can't speak to how helpful or responsive they would be.

We used to use TFS.

The product is quite straightforward, especially since it is on the cloud. It makes it very easy to set everything up.

We have three people able to deploy and maintain the solution.

We did not use an integrator or consultant for the deployment of Jira. We handled the process ourselves. 

We pay for a yearly license. 

We primarily use the solution ourselves, as customers. 

I'd rate the solution at a nine out of ten. 

I would recommend the solution to others. It would be ideal if it offered better tool integration, however, other than that, we've never had issues. 

Public Cloud

I use the solution for software project management and software lifecycles. Jira covers the entire process from requirement analysis to deployment. 

I prefer Azure DevOps and Microsoft Ecosystem to Jira. 

I consider Azure DevOps to be more user-friendly and to provide a better user experience. I feel Jira to be a bit difficult to work with. I specifically recall that i encountered difficulties with Jira when I wished to receive or generate a report. Azure DevOps offers a simpler and more user-friendly panel than Jira. Jira's reporting panel is not user-friendly and a bit on the difficult side. Azure DevOps also offers more options for generating queries and reports, especially when it comes to great dashboard visualization capabilities for the monitoring of one's project. This poses a big problem with Jira, as Azure DevOps does a better job of providing this feature. 

I find the dashboard to be Jira's most problematic feature. I do not like it and feel Jira is troublesome when it comes to visualizing the reports. These should be improved. 

Azure DevOps offers more simplified processes, maintenance and development than Jira. 

I used Jira for around one year, at which point I left my previous company and made use of it in the new one I joined, where I continued to do so. 

I find the solution to be stable, though a bit hard to use. 

We have not encountered difficulties with the scalability. 

We have had no issues with support. As with Azure DevOps, we take advantage of the open community and forums for resolving any issues which may arise. 

I prefer Azure DevOps and Microsoft Ecosystem to Jira.

I consider Azure DevOps to be more user friendly and to provide a better user experience. I feel Jira to be a bit difficult to work with. I specifically recall that i encountered difficulties with Jira when I wished to receive or generate a report. Azure DevOps offers a simpler and more user-friendly panel than Jira. Jira's reporting panel is not user-friendly and a bit on the difficult side. It also offers more options for generating queries and reports, especially when it comes to great dashboard visualization capabilities for the monitoring of one's project. This posed a big problem with Jira, as Azure DevOps does a better job of providing this feature.

I find the dashboard to be Jira's most problematic feature. I do not like it and feel Jira is problematic when it comes to visualizing the reports. These should be improved.

Azure DevOps offers a more simplified processes, maintenance and development than Jira.

As with Azure DevOps, we take advantage of the open community and forums for resolving any issues which may arise.

We make use of the solution free of charge. 

My recommendation, for sure, is that a person go with Azure DevOps. 

I rate Jira as a six out of ten. 

My people use ASS. I can define spins, I can define roadmaps, I can define components, I can do releases, I can define all kinds of issue types, heartbeats, some of those things. I'm using it for both business and software. In software we have Scrum and Kanban onboard, whereas for business we have the service and then there are those other options. We have multiple use cases. I'm the director of the company. 

I like almost everything about Jira. It defines how we track time and the way we define permissions. We can create multiple boards for the same product backlogs. 

I think that for users the solution is very intuitive but for project administrators, the way the product is defined is not very intuitive. There are too many ways to do the same thing. The setup of Jira sometimes becomes very, very cumbersome and difficult. It's not very easy for people on the project admins to really understand how to set up the product because of these features. If they were better organized and the documentation improved so that people would actually be able to figure out how to use Jira, that would be helpful. There are not many videos and it can be very challenging for anybody not familiar with the product. There are 50 users on the project I'm working on. 

I've been using this solution on and off for the last eight years. 

The solution is stable.

The solution is scalable.

We haven't really used technical support. 

The initial setup takes a bit of time because it has so many features that you should be aware of, but of course it provides a lot of out of the box features that you can use right away. You can set up in 10 minutes or 10 days, it's very rich. I was able to do the deployment myself with some extra help. 

For up to 10 users, the solution is free but above that there are licensing costs.

I would rate this solution an eight out of 10.

Public Cloud

We use Jira for software for product development, planning, some hardware product development, and for some solutions and services. Other teams in our company use Jira for scheduling daily work and daily tasks and try to organize or manage products and projects.

There are a lot of different plugins for Jira. Unfortunately, we did not test so many and the big pain point for us is the rigorous handling and the roadmap of Jira. We have a portfolio and structure plugin and we have our story map plugin in Jira. I am a scrum master and coach in my company. My colleagues aren't so educated on these plugins. So first we have to improve all knowledge with these plugins in Jira, to improve or efficiency in the roadmap and for these topics.

The performance is not so good sometimes. I know that fully depends on the implementation and the IT environment of Jira or the version of Jira installed. The performance is sometimes not so good. I would like to have a better response time from the Jira server. And it fully depends on the administration side of the Jira.

I have been using Jira for more than 10 years. 

It's a very stable system. 

My company has different locations in the world. We have maybe 1000 or 1500 people using this solution.

It is easy to scale and expand.

I am not a Jira administrator. So my feeling as a user of the Jira is that Jira is a very efficient, very good tool and a very stable tool from my perspective.

We haven't contacted tech support because the specialized team does it every time.

Everything is delegated to the team inside the company

We also used Mantis. I can't compare the two because Mantis was very different and that tool is very old. The function was very different in Jira. So when we switched from Mantis to Jira, it was a very big step. 

We have a specialized team that did the installation and does upgrades.

I prefer some different practices, like story mapping and inbox mapping or strategy planning. The story mapping is included in all Jira installation. It would be good to see some features for strategy and portfolio handling planning in Jira. I have used Aha! and this tool has a very good framework with a good toolset. The toolset for strategy planning, toolset for portfolio handling, toolset for product handling, and toolset for daily work handling is very good. I think the Aha! team did very good work. I know that this company is an American company and is a competitor for Jira and for some other tools. Unfortunately, I never heard about this tool before and don't know any other company using this tool, but the tool is very impressive. There are a lot of good features. It would be good to see something like that in Jira.

I would rate Jira a seven out of ten. I would give it a higher number if the features that I mentioned for the strategy planning would be included in the framework.

The primary use case is for software development teams to manage their work.

The most valuable features of this solution are workflow and reporting.

The team construct could be simplified. We use Jira with Tempo Planner, and Portfolio for Jira, and at times it is not always clear. With Portfolio, it's the same as Jira but with Tempo, it clashes. It's not a seamless transaction.

We would like to see integration between Tempo and Jira. For example, if I create a team in Tempo, I would like to be able to use it and re-use it Jira as well. 

In Tempo, if you create a team then you are able to link that to a project in Jira. I would like to have that same capability, where I can link to Portfolio for Jira. Specifically, if I create a team in Tempo then I want it available in Portfolio. When I am planning the work for my team, it would be easier to have that capability available.

I have been using Jira for approximately four years.

It's a stable solution and we have not had any issues.

Jira is scalable. 

We have more than 13,000 users and we have not experienced any issues with the performance or scalability. We are able to scale pretty well. 

I work with Jira on a daily basis, as well as offer support to users and guide them into making the best use of it.

We have a relationship with Atlassian. I have not personally had to contact technical support, but I do know that we have a technical account manager to whom we report any issues.

My advice for anybody who is implementing Jira is that it easy to use but you want to understand what your requirements are. You want to know what you want to use it for, and what you want to achieve by using it. 

With Jira, you get what you input, in terms of your data. For me, I get what I need out of it.

I would rate this solution a ten out of ten.

On-premises

The primary use is task management. It has performed okay. It is easy to configure and maintain. It's quite simple to track tasks, then link with other applications/solutions from Atlassian, like source codes.

• Visibility
• Avoids emails and exchanging information in an informal way. 

I would rather have a tool that we do everything on. Also, we have access to end user policies where we can configure them and give access to the correct person. We have tracking of who works on what and why over the history of a project.

Workflows, because we cannot employ a different approach depending on the speed of the project or customer. Whether it's research, engineering, or maintaining the process, we can cope with processes easily without adapting the tool, but adapting the tool to processes.

There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes. So, you have to use some add-ons and create a lot effort to obtain information from the tool. Thus, you have to adapt to the lack of search that the tool does not offer.

Three to five years.

So far, so good.

I don't see any problem with it.

In the past, I had training from the distributors and it was okay. 

The tool is very easy to use. What is important is that we don't have to wait so much for contracts or more hours to have support. This is something that we have, and it is good for this solution.

Everywhere that I worked, we started by using spreadsheets, then we moved to some free tool, and finally to JIRA.

As far as I know, the initial setup was very simple and straightforward.

Understand your own process: What you are looking for, the size of your company, what your budget is, and the larger plans for the future. There are tools that scale better than others and there are solutions that fit to both small and big teams. There are tools which scale better for larger companies. 

Most important criteria when evaluating a vendor: 

• We evaluate the company's strategy.
• If they bought an legacy solution to add to the portfolio or if they are developing from scratch.
• What are their plans for the future?
• What type of support do they have?
• What is their business model? 
• Do they have domestic experience or not?
• Are they focusing only on a few customers, and the size of those customers?