Jira Reviews

It is mostly used for communication, managing requirements, managing defects, and managing stories. We don't communicate much through Outlook. The majority of the work-related issues are assigned to us, or we assign them to developers through this solution. I've been using this solution for managing requirements and defects. I have also been using it for logging user stories and general communication.

Best in ensuring 100% test coverage through forward and reverse traceability matrices capability that allows users to track User stories, SRS, Test Cases, Test Instances & Defects all using simple links. 

The most valuable feature is the feature of assigning. Whenever I have an issue, Jira doesn't stop at just letting me describe the issue. I can also assign the issue to a developer, and the developer gets notified about it. After he is able to work on it, he can update the status and revert back to me through the same platform. It really avoids a lot of communication over email and phone. This the feature that I really like about Jira. I always use Jira with my team.

Produce improvements suggestions:

User Interface/ User experience could be improved by expanding on visual capabilities of links such as  Stories, Requirements, Scenarios, Cases, & Defects.

User Dashboards could be improved by increasing ease of use of charts and other interactive options such as Boards.

I have been using this solution since 2011.

It has been stable. I haven't had any downtime or issues with stability. It has been working as expected.

In terms of integrating Jira with other apps, I've actually used Jira to connect to ADPART or other client defect tools. Sometimes, I had to use the connections, but it was not a problem. There is a standard procedure where I had to request for the details, and after I got the details, I needed support from the client to get it connected. There were no issues, and the process is quite standard. It is not fast, but it requires some time.

At my current company, only I am using this solution. We are a startup, and we have less than ten people working here. However, on my client's site, a lot of people are using it.

I've used their technical support only once or twice in my entire experience with this tool. Once, I was not able to log in, so I had to call them, and the other time, it was a problem with my virtual machine. It was not a problem with the tool. I was having problems getting in. I raised tickets, and then I had to call them. It was nice, but it took a little bit of time. Overall, the customer experience was all right.

Before this, I used an HP tool. I started with using Quality Center, and then I upgraded to ALM, and ever since, it has been Jira. Jira is open source, and some of my clients prefer open source, and they have been using it for a long time. Before Jira, ALM/Quality Center was my major go-to tool.

It was straightforward. I just got the details from the client, and I started using it.

Save by reducing errors and improving accuracy.

Start with requirement. If requirement requires tight security and confidentiality, it is highly recommended to employ expert assistance. Whereas if the requirement is agile in nature and is at very initial stages, it is best to start leveraging open source to some extent.

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. 

It is essential to track efforts right from the beginning of the project i.e the from the day of planning and incubation to delivery and deployment. 

I have been the product manager for several years. I use it day in and day out to manage my team. I manage two teams at the moment and they are pretty large teams. Each has a minimum of about 12 people. We use not just agile, we use a scale model framework. All the work is managed through two pieces of software we use. One is called Jira Align. For the portfolio level software, what Jira bought recently, the previous name for the software was AgileCraft. All of the portfolios and features come loaded in Jira Align. From there, they will be composed into stories in Jira. That process is done using programming preventative planning. We do it every three months.

All of the stories are tracked. We have a workflow defined and we have statuses defined. As the team works on the story, the story moves from one status to another and we close them when everything gets carried over to the production release.

The workflow is the most valuable aspect of the solution for us.

The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view.

There are excellent reports that come out of the data for every sprint so that you can do metrics on each. You can measure how the team is performing with respect to burn down charts, or with respect to how many story points were produced, or how many stories were moved out. For this, you can gauge the performance of the teams very effectively.

The solution needs performance improvements. We see that a lot of times it's clocking whenever there's any abuse.

When we switch from one view to the other, it takes some time before that view is presented. The performance for different dashboards, whenever they are loaded, it takes more time than you're comfortable with. Whenever you move from one dashboard view to another dashboard view, then it should come up quickly. Right now it takes a long time and sometimes it clocks. The overall product performance, whenever you switch a view is what they need to work on.

Whenever you edit a story, whatever you have changed takes a bit of time to save.

The integration between Jira and Jira Align needs to be better. There's a lot of differences between the two systems. I believe what happened was Jira bought this software from a different company called AgileCraft. And that integration is still in process, and, because of that, there's a lot of differences between the statuses. That sometimes creates a lot of confusion for senior management whenever they're reviewing performance across teams. Better integration between Jira and Jira Align is on the top of my "most desired upgrades" list.

The solution should improve performance when there are multiple users.

I've been using the solution for about seven years now.

Whenever you load different views, it takes time. That's the only major issue. I didn't see any major glitches due to the fact that Atlassian is really good at catching them. The stability of this product is really great. I've been using it for, as I said for six, seven years now. I'm never unhappy with it.

Our entire company, whenever there's a new division that goes into the agile mode of developing software, brings on Jira.

It's really scalable, however, at the same time, you need to really throw hardware at it to offer better response times when you add users. That goes without saying for most of the software.

We currently have 2,000 users on the solution. We plan to continue to increase usage in the future.

We have an internal tech support team for Jira. We contact them whenever we run into issues. We have a platform for IT tickets. We use that to call them. I haven't directly called Jira Atlassian at any point, so I can't speak about their direct technical support.

I have used other packages for agile project management.

I wasn't involved in the initial setup, however, we have a Jira administrator and they have a group, and that handles it. I implemented Jira for my teams. I added users to roles on the system. Roles such as developer, administrator, approval, managers, etc. That is all done by myself. In terms of that task, and setting up a project, it's fairly easy.

Implementation is a multi-year process. Right now, the whole company is on Jira. Whenever there's a new group, it gets added, and a new team is created. It's always a work in progress and it's not very time-consuming.

I would say the training of people on how to use Jira effectively takes some time. It's very intuitive, however, at the same time, a little training goes a long way in utilizing the software in a much better manner.

We are using the latest version of the solution.

It's a great piece of software. If you really want to do agile software project management Jira is definitely should be a top choice for you.

I'd rate the solution eight out of ten.

We primarily use the solution for product development efforts and documentation. We use Confluence as well for documentation.

Most of my work is keeping track of what's been going on and identifying what is blocking future work. What I like about this solution is you can create a consolidated customized dashboard out of your files to identify what's been going on and identify who has how much data assigned to them. You can begin to understand where roadblocks are and how to streamline efforts effectively. It's been helpful. 

The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything. While it should be a standard thing across the company to have labels created in certain way, the system should be able to pull up suggestions of labels that are close. 

The product could be more intuitive. 

If something isn't getting resolved, we generally aren't getting any alerts to warn us to this fact. We don't get any visibility on if something's been open for a few months even if it should have been closed after a few days. We need some sort of system that shows us items that are lagging.

I've been using the solution for about six months to a year or so. It hasn't been too long. Our company has been using it since they started doing development work.

In my experience, most of the time it's very stable. Sometimes we have a few bugs here and there in Jira. However, it doesn't affect our work in a very big way. It doesn't crash or freeze. It's reliable.

I'm not sure about the whole company, however, on my team, we use it extensively. We have around 30 to 35 people using it on this team. Obviously, they are using it on other teams as well, however, I don't know the count of each team.

In terms of scalability, we are able to add new users as needed, and that has never been a problem for us.

I've never had to reach out to technical support. I don't know how responsive or knowledgeable they are.

I didn't previously use another solution, Jira is the first product I've used for this purpose.

I actually was not involved in the initial process of the setup, therefore, I can't comment on the process. I have no idea as to if it was difficult or straightforward.

I'm not aware of any regular maintenance that is needed on the product.

I don't deal with the financial aspect of the product. I cannot comment on if it is overly expensive or not as I don't handle billing or payments.

We're just a customer. We don't have a business relationship with Jira.

I'm not sure of which version of the solution we are using.

I'd recommend others go ahead and try the trial version of the product. If, after that, it seems to fit your needs, a company should go ahead and implement it fully.

Overall, I would rate the solution nine out of ten.

Our primary use case is for our own network operations, and integrating via API with our customers network operations teams.

It created excellent data points and summary with up-to-minute information.

The informatics is the most valuable feature. It captures what we need.

The user interface could be better, but the stability is definitely there and the accuracy is good.

The GUI should have much better features like more graphical illustrations. There are some cases or benchmark data that we are trying to capture and customised into a graphical pie chart summary dashboard, but unfortunately JIRA is not able to do that.

We implemented JIRA six months ago.

The stability is good. We have around ten users as a start. 

Impressive

We have contacted technical support. Their response was prompt. 

The initial setup is not that difficult, but it's not that simple either. That is why it took us  about three to six months to get it up and finalized.

Via our in-house.

Right now the price is fair but once they move to the cloud, that model may not be attractive anymore.

It is an excellent tool to summarize and get our stacks of data into a platform for operational overview and interface tracking. It is very useful for us. 

I would rate JIRA a nine out of ten. Not a ten because of the GUI pie chart. The beauty of the dashboard is not perfect, so I subtracted some points.

We use the solution primarily for project management. We organize our work by projects with epics, et cetera. Below that, I believe we are using a Zephyr plugin for QA. We don't use it for product planning.

I would say it's a necessary evil to use a product such as Jira. All of these solutions are a necessary evil. They all have their pros and cons.

For what the solution does, it's fine.

The solution offers a lot of plugins.

The solution is very configurable.

There's a bit of a learning curve, which I'm not a huge fan of. It's not exactly user-friendly per se.

I would prefer it if the solution was more intuitive.

There are just so many options, that it's pretty overwhelming as a product. There's too much to focus on.

We do find that we need plugins and have created integrations with more robust analytic solutions than Jira provides.

Personally, I'd like it if there was more flexibility in how you could manage the backlog at a project level.

I've been using Jira for about six months. It hasn't even been a year yet. The solution is still very new to me and I am still learning.

The solution is very, very stable. There's no problem in that sense. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

You can easily scale this solution. If you need to grow it out to meet your company's needs, you can do so. That's not a problem.

We have about 300 users on the solution right now. They include developers, administrators, senior leadership, analysts, designers, and project managers.

I haven't used technical support at all. I can't speak to their reliability or level of knowledge.

Although I wasn't hired at the outset of the company, it's my understanding that they've always used Jira as a solution.

I wasn't involved in the initial implementation of the solution. I just started working with the company six months ago. Honestly, I'm still learning the solution.

I don't have an opinion on the pricing or licensing. It's not really a main concern of mine. I don't have access to any information about what the company pays.

We're just customers. My company doesn't have a professional relationship with Jira.

I'm not sure which version of the solution we're using. I'm not sure of the last time we updated the solution. I've only been at the company for six months.

I'd advise other companies to dedicate two full-time people to learn the solution and train other team members. It's a big learning curve for users. It takes time to get into it. Having dedicated trainers would help onboard people.

Overall, I'd rate the solution seven out of ten. If it was more intuitive, and there was less of a learning curve for new users, I'd rate it much higher.

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.

We use Jira for multiple uses; project management, task management, and we are starting to use it for release management.

The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on. For these results, it is very helpful. I also like the customization that we had for the workflows for the different issues, it's quick and easy to customize. The reporting is also easy and the dashboards that they provide are really helpful and simple. It does not need a lot of experience with reporting and presentation to get to what you need. Also, most of the advanced reports that you need to create can be exported as Excel files.

I have been watching an issue develop. There is a difference between their cloud and their  server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it.

Additionally, it would be really nice if they added some custom reports so that you could build your own report through any open source or commercial plug-in like Crystal Reports. That would be much easier for them to accelerate. You can create a report template and use it frequently.

There are a few features I would like to see in the next release. For example, the layouts could be easier to configure on the screens. I know it's easy to customize. For each issue type you can create and modify your screen. But it would be easier if you could enlarge, copy, clone, and visualize them in a model in a visual way. It's really hard for me as an admin to compare different screens or even to copy one screen with one additional field. I believe that is creating a lot of confusion for end-users because usually admins are looking at each field independently, where it's located, in which position, and which screen. So that all needs to be improved from an administration point of view to make it easier to visualize and compare between the screens.

I have been using Jira for almost a year now.

In terms of stability, it is fine.

The initial setup is easy and straightforward. The deployment is very easy. It just took one server.

It took one day to set up the database and then start the configuration. That is straightforward. And I believe they have a newer deployment model that they can deploy on Docker and other container platforms.

I did it myself with some help from other team members.

Jira is an amazing tool, but to get the process streamlined is a challenge. So don't start from Jira. Start with your process first. Agree on the workflow, identify all the stakeholders, and then from there you can go ahead with Jira and implement anything.

On a scale of one to ten, I give Jira a 10.

Everything already provided is perfect. We are using Jira perfectly for one year now and it's absolutely great.

The primary use case of this solution is to manage work, to distribute work to the teams, and we use confluence as a SharePoint for documents and to use AgileCraft.

This solution is easy to work with. It's easy to understand, and easy to navigate. 

it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do.

In the next release, I would like to see better integration with other software. Many companies have a lot of peripheral systems. They have ServiceNow or they could have something else. How do they integrate your stories, your sprints, or if you have confluence, or SharePoint when you start using Jira? 

The challenge is when you have someone who is not using confluence, but they have SharePoint or ServiceNow.

How do we connect, or integrate our stories with Jira, so we don't have to have the information in three different places? 

The integration and integration threads would help Jira going forward.

I have been using Jira for more than one year.

This solution is stable. I haven't experienced any issues, it works fine.

We have approximately 100 users. It is not used concurrently. There could be anywhere from 20 to 30 users in a day.

We have yet to explore the scalability, but we hope that it is easily scalable. For us, that was the purpose of using this solution in our organization. We plan to use SAFe, a scalable scaler, scale agile.

I have not contacted technical support,

The initial setup was done by two local employees.

This an area that I would like to explore more from an admin perspective, on how to set up teams, what are all of the things we can do, and to set up the right way so that we can get the most potential out of the software.

I am not involved in the pricing. We have a sales team to procure our licenses.

I don't feel that price is an issue.

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

It's difficult for me to tell you everything that Jira has to offer when I am still learning. I am trying to educate myself to have a better understanding. I want to learn more.

I would rate this solution an eight out of ten.