Jira Reviews

We maintain all space-related information in Jira. We track all stories and add tasks to identify specific services. We pull the relevant functions onto the screen. We follow a two-week sprint cycle, completing sprints accordingly. We proceed to make a release. We conduct testing activities, whether manual or automated. If bugs are identified, we fix them. The customer story remains in the loop until we move to the release cycle. Upon release, developers can automatically deploy the code. After deployment, we proceed with user acceptance testing and move to the front end.

Everything is tracked in one place.

There could be an improvement in loading files and images for more than 50 MB. It would be good if it allowed more than 100 MB.

Additionally, Jira analytics needs further development to analyze code, but we should keep the queries. This will allow us to delve into the details of completed tasks, work in progress, and pending items. However, more information regarding graphical representation is still required. Considering the number of test cases, it's crucial to have comprehensive data on completion status, logs, and retesting. Jira excels in providing such detailed information.

I have been using Jira for 6 years.

The product is stable.

I rate the solution’s stability a nine out of ten.

The solution’s scalability is good.

55 users are using this solution every day.

I rate the solution’s scalability an eight out of ten.

We receive technical support. Some challenges may arise, particularly in labels, but we receive assistance.

Positive

I have used ALM before. It has high pricing, considering the maintenance and shipping costs. Although the features are new, if we compare them to Jira, ALM still lags.

The initial setup is easy and takes a few hours to complete.

I rate the initial setup a nine out of ten, where one is difficult and ten is easy.

A third-party vendor handles deployment. They will automatically execute the small instructions. Based on that, they will create a charge code, seek approval from management, and then proceed to deploy the particular feature. While auto-deployment is happening, we'll validate it once it's done. If everything is good, we'll release it. If there are any challenges, we'll roll it back.

The product is cheap.

I rate the product’s pricing one out of ten, where one is cheap and ten is expensive.

Jira is easy to use and maintain; everything is in one place. Minimal maintenance is also required. 

We have our developers to maintain Jira. They will develop whatever we require for labels and provide them to us.

If you want to inform me about the adaptations for scaling Jira, it will be convenient to use Jira, but most of the reports will be easy to generate. We integrate with Git, making the process a bit easier.

Overall, I rate the solution a ten out of ten.

I use Jira in my company for my projects or the tasks assigned via the tool. I also use Jira as a scrum tool.

The solution's most valuable feature is that I used the tool to deal with bugs. In my project, with the bug assigned to me by my company, I was given the backlog and the code. Whenever I had to add it, I used to request Git for code push, pull, and merge, and then I used to paste that GitID into Jira. It was very easy for the other developers to handle whatever code I did.

At times, I am not able to report a bug. Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required.

I have been using Jira for two years. My company is a customer of the tool.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

With the latest versions being released, I feel Jira is being improved daily.

My previous organization used Jira, and now, my current company also uses it.

The solution's technical support needs just to understand the customers' environments and improve or provide a better version of the tool. I rate the technical support a nine out of ten.

Positive

The product's initial setup phase is easy.

The solution is deployed on the cloud.

It is an affordable tool.

From a project management perspective, my project manager assigned some Jira tickets, and I started to do it on a weekly and daily basis. I send a request to a Jira ticket to open it, and during the process, I start describing how I am replicating that issue, explaining it in that Jira ticket. After that, I resolved that Jira ticket put that Git code in the expression part, and submitted it.

Regarding reporting and analytics features, my company uses Jira for software development projects as if it were a single tool. My company uses the tool in a manner where we send requests to one developer, and they open a Jira ticket using the email. Every day, they update so that everybody is able to see it without any description, while my team can see what the developer is doing daily. If a developer is updating, everybody can see that in the company. The tool is very easy to use, and it is easy to understand areas like script planning, story points, and backlog grooming.

I recommend the product to those who plan to use it. I worked with two scrum tools. In Azure also, my company uses scrum, which is a little bit uncomfortable for me, but I am very comfortable with Jira, a major reason I suggest it to other people.

I rate the overall tool a nine out of ten.

We use it for requirements gathering. We raise our tickets; it takes tickets in the engine. We also use it for bug tracking and integrate it with the X-ray for testing.

Jira is a one-stop solution for all the requirements of an Agile project, including SSL. It's easy to use, and it also offers excellent notifications.

Jira has integrations with almost all other build management and alerting tools, both open-source and licensed ones. There are limitations to its data.

It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray. It would be beneficial if Jira included modules covering testing elements such as test planning, mapping test cases to requirements for traceability, tracking execution status, and managing different branches before release. Since Jira lacks robust support in these areas, we rely on additional tools like X-ray, which can be integrated with Jira. If Jira could incorporate these features internally, our processes would be streamlined.

I have been using Jira for 5 years. We are using the latest version of the solution.

I rate the solution's stability an eight out of ten.

Around 100 users are using this solution. It is scalable too.

I rate the solution's scalability an eight out of ten.

Customer support is good.

Positive

Jira is not difficult to install. We have an IT help desk team to take care of admin configurations, installations, etc. Everything is managed by different teams.

There are roughly around 50 people for deployments or maintenance overall.

The product is moderate and has a yearly subscription.

I rate the product's pricing a five or six out of ten.

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.

My advice would be to consider having a Jira license. There's a level of customization available, along with flexibility in pricing plans, so you can tailor your request according to your needs. This allows us to access features that align directly with our requirements.

Jira has integration capabilities with almost all build management and alerting tools. It offers seamless integration with both open-source solutions and licensed ones.

Overall, I rate the solution a ten out of ten.

We use Jira as a communication tool for tasks and epics. Everything is in one place in the ticket, and it's helpful to communicate with the team. We don't have to use Slack and other platforms to track information related to tasks.

The most useful features are the Kanban dashboard, the ability to create tasks, bugs, epics with child issues, time estimation, and Jira reports. The dashboard helps in tracking tasks and projects easily. Time estimation is crucial for my team to estimate tasks accurately, and the monthly reports are helpful for monitoring progress. We can see everything in one place, which improves communication within the team.

Sometimes it's hard to set up the dashboard for the team lead. For example, I can see tasks selected for development but not UAT tasks. It would be beneficial if the setup was easier. I understand Jira is a comprehensive tool, but dashboard setup could be made more user-friendly.

We've been using this solution for about two years already.

The stability of Jira is good. I have faced issues only once. I would rate it nine out of ten.

Jira is pretty stable and scalable. On a scale of one to ten, I would rate it nine for scalability.

I haven't contacted customer support yet.

Positive

My company also uses Azure DevOps dashboard. I prefer Jira because its interface is simpler and easier to use than Azure.

I am just a user of Jira. The dashboard setup is done by our team lead, so I'm not sure how to set up Jira.

The price is regular for this kind of tool. However, my company hasn't bought Confluence integration because of the price. We are fine with Jira, but would like to have integrations if it becomes cheaper.

Feel free to try it, and you will love it. The biggest advantage is that you can see all of the project in one place on the dashboard, track your estimation and time, and see your progress. I rate Jira nine out of ten.

ira is a very complete tool in the tech industry, helping in deploying software. Jira is a very strong tool for a corporation with a team to track and monitor all the tasks that have been defined within a project. It helps teams work and collaborate faster to improve performance. 

I think one of the most powerful features in Jira is the customization of fields and workflow. Jira helps in projects consisting of a workflow by providing templates with the return workflow, we can even modify the workflow and the fields. 

I think the GIS can seem too complex for some people because there are a lot of structures in the software itself. Users need to understand how Jira works, how to define Apex, how to use the storage and many other things. Each template provided by Jira has a different functionality, so users need to explore further about the functions of Jira, especially for the setting and configuration factors. There might be users out there who are unaware of the features in Jira. Otherwise, users will be confused about how to use this tool as it's very complex. 

The product is stable, and in terms of performance, it's really fast. The support team from Jira always informs users in advance, for example, if there is any scheduled maintenance or anything related to the performance tab. I believe Jira also creates maintenance schedules by considering the non-productive hours for each country. Hub fixes and new feature addition time are also planned by Jira for users. 

Jira has a great Knowledge Center, for any kind of questions about how to use the product or other FAQs. Users can check the Knowledge Center before raising a ticket to Jira support. But for some cases, if someone creates a ticket, Jira support is very proactive and follows up on every ticket to provide a solution. Thus, support from Jira is great. I would rate customer support a nine out of ten. 

Positive

Previously before using Jira, we were using Google Workspace because it also has collaborative features. But I think it was missing a lot of features compared to Jira. Jira is specifically created for product or software development, so it's suitable for our business product. Jira has also gone through a lot of improvements over the years since we are using it. 

Not much time is needed to install or configure this tool. You just need to register and subscribe before the tool is ready to use.  

I would rate this product an eight out of ten. 

We are using Jira to plan and manage projects, including tasks, sprints, and releases.

It allows teams to create, assign, and track issues. It supports various agile methodologies like Scrum and Kanban, providing tools for backlog management, sprint planning, and burndown charts. 

It offers robust reporting capabilities, allowing teams to track progress, monitor team performance, and generate visual reports.

Jira's user-specific dashboards and reporting capabilities provided insights into individual and team performance. This promoted accountability and allowed our development team to recognize and reward high-performing team members.

Jira's collaborative features, such as comments, notifications, and real-time updates, facilitate better communication. Teams can discuss tasks, provide feedback, and track progress in one centralized platform, leading to smoother workflows. 

Tracking bugs, feature requests, and development tasks was cumbersome. It was difficult to prioritize and assign issues, leading to delays in issue resolution. With Jira's issue-tracking capabilities, we can create customizable workflows. This enables users to capture, categorize, and assign issues with ease. As a result, the development team can address issues promptly, improving product quality.

Jira's native support for agile practices, including Scrum and Kanban boards, allowed our development team to embrace agile methodologies seamlessly. This enabled them to prioritize features, plan sprints, and adapt to evolving client needs more effectively.            

Jira's user-specific dashboards and reporting capabilities provided insights into individual and team performance. This promoted accountability and allowed our development team to recognize and reward high-performing team members.

Jira required a significant amount of system resources, particularly for larger organizations with extensive workflows and numerous projects.                            

The high level of customization and feature-rich nature of Jira are confusing for new users, requiring some time to learn and navigate.

Administering Jira, especially in large organizations with complex workflows, can be challenging and may require expertise.

I have been using Jira for issue tracking and task management for the last seven years.

We did not previously use a different solution.

Jira is used for all the project management, on all the stages of project management. So then we create a Kanban board and move on to creating the stories.

We create the story points, break down the requirements, and then create the Sprint accordingly. Based on that, we can manage in Jira how many user stories we will pick in what Sprint. And based on the dependencies of the user stories, this is the flexibility that Jira provides. Then we have also got various, you know, sub-tasks, which we have to complete to accomplish the DoD (Definition of Done). We can mark the Sprint as complete when these particular tasks are completed. So that gives very good monitoring of the project where the project is

going on.

When it comes to the testing part, so testing is end-to-end on Jira. We can take the user stories based on the acceptance criteria. The test cases are created in Jira, and the business analyst team reviews those test cases. Based on their feedback, the test cases are updated. Those test cases are being executed. So there is clear tracking of the test execution, and all the test cases are also linked with the user storage. We have end-to-end tracking of what test case is executed for what user story. So that is the best part of Jira.

The monitoring, flexibility and tracking are really good in Jira.

When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect.

I have been using Jira for eight years. 

Jira is a stable product. I have seen the growth in the solution’s stability for the last eight years. The current version is quite stable and is a robust system.

Overall, the solution is scalable. Jira is quite easy to scale. If we have five projects working on Jira and we have about five more projects to be incorporated, it's easy to install Jira for those five projects as well. Presently, twenty five thousand users are using Jira. 

We have been using this for the last eight years and we are quite accustomed to that. We don’t need much support from Jira or Atlassian. Yes, but we have got an enterprise version of that, and their support is quite quick.

Positive

I was using HPE Quality Management Tool.

The initial setup of Jira is very easy. I have been an administrator, so I would say that because used to it. But in comparison to other systems, yeah, it’s quite easy and user-friendly. The deployment takes two to three days of time. Forty people are required for the maintenance of the solution.

I implemented it myself as an administrator of Jira.

Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost.

Use all the reports which are generated. You have to make a system for the process. Here is a small example during a subtask. The time input via the source is not mandatory. But you have to make it mandatory either from the back end.

You’ll not be able to fetch the reports on the performance, the health of the project, capacity management, or IT management if the data is not input properly. So this is something which people most people don’t take care of as a Jira planning. But when you plan a project, you have to plan these things.

I rate the overall solution a seven out of ten.

We use it for project tracking. We do software development. We implement software development lifecycle, and we use Bitbucket for CI/CD pipelines.

We have a lot of vendors operating on multiple projects, so in terms of operations, we need to maintain the backlogs of different projects. The sprint approach for roadmaps is cool in Jira, but we are looking at whether the same option is available in Azure DevOps because one of our clients is looking into using Azure DevOps.

Jira has a good reporting system. It also has an API, so we can do all sorts of reporting. 

There are a lot of things. A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product.

I've been using this solution for five years.

It's stable. The stability on the cloud is 99%, but we have deployed it on a virtual machine. 

Both cloud and on-prem deployments are scalable. I'd rate it an eight out of ten in terms of scalability. 

Our clients are small and medium enterprises.

I'd rate it a nine out of ten.

Positive

The setup on the cloud is easy. I'd rate it a nine out of ten in terms of the ease of setup. The on-prem setup requires some work. I'd rate the on-prem setup a five out of ten in terms of the ease of setup.

We have four people who are working on Jira maintenance.

It's not very cheap. It's also not very costly. I'd rate it a five out of ten in terms of pricing.

I'd recommend it to others. Overall, I'd rate it an eight out of ten.