Jira Reviews

We basically use the solution for trying to develop a product end-to-end. It's assisting us in having hardware and software come together.

The solution provides users with clarity in terms of the scope of work in a given timeframe.

Managing the backlog and being able to move work around and drag it around in order to replan it to certain sprints is the solution's most valuable aspect.

There are many areas where improvements can be focused.

There's a really steep learning curve for configuration. I'd like them to simplify all of their configurability yet not remove the configuration options.

I've been using the solution for two years.

We haven't had any noticeable stability issues. There are no bugs or glitches. It doesn't crash or freeze. it's reliable. 

There are some issues with scaling. It's difficult to consistently configure multiple teams within a single product.

We have about 150 and they're robotics engineers, software engineers, firmware engineers, PMs, and product people. Anyone that would be on a product development team uses it.

We will maintain usage and intend to continue using it for this deployment. I cannot speak to if there are plans for expansion.

We've never reached out to technical support. I can't speak to how helpful they are. 

I'm also familiar with Azure DevOps, which is easier to set up. However, this company has always used Jira.

The initial setup has a moderate amount of difficulty. It's more complex than, for example, Azure DevOps. I'd rate the process at a three out of five.

The deployment took about three months. 

I'm not sure how many staff are needed for deployment or maintenance tasks. 

We handled the implementation process in-house with our own team. We didn't have any consultants or integrators to assist us in the process. 

It's hard to put a number to the ROI we're seeing. It's more qualitative around the structure it provides than any kind of cost savings. 

The cost is about $10 per user, per month. 

There is a perception with Jira that they try to nickel and dime you quite a bit.

For example, they'll often say "Oh, you want this little feature? We'll charge you $3 per month per user." Whoever's signed up to your account they will charge you, even though you might only need five people to sue it from a 150 person team. That's excessive.

Compare that to Azure DevOps where withAzure DevOps, you just pay $20, and then you deploy that extension to your instance or tenant. With Jira, they charge you a dollar or $2 per active account in your tendency even if not everyone in my tenancy needs to have that extra feature set.

Since we use the cloud, we are using whichever version is currently deployed there. It's updated automatically.

I would recommend Azure DevOps over Jira.

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

We use Jira for various purposes. Firstly, we use it to gather requirements by raising tickets and tracking them in the system. Additionally, we utilize it for bug-tracking. 

What I really like about Jira is that it ticks off all the boxes for any agile project. It's easy to set up, easy to use, and it has excellent notification features. Jira is the top choice for anyone working on agile projects like ours.

The tool lacks support for testing aspects, which means we often rely on integrations with other tools for testing purposes. If Jira could incorporate testing modules within its platform, it would eliminate the need for external integrations.

I have been working with the product for five years. 

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

Jira is scalable. I rate it an eight out of ten; we have nearly 100 users. 

Installing Jira isn't difficult, but our administrator or IT help usually handles it, so I'm not directly involved in the installation process. We have around 50 resources for deployment and maintenance. 

Jira is worth the money. 

I rate the tool's pricing a five out of ten. It's paid yearly. 

My advice would be to explore the different licensing options available for Jira. There's a level of customization in pricing to tailor it to your needs. I rate it a ten out of ten. 

We use the solution primarily for the IT development processes since we also develop some internal software and integrations. We use it for IT support. We also use the project management features. We help create some custom projects within Jira and assign or dedicate some of the projects to top-level projects. Some are epic projects. We have our own custom project structure within Jira.

The product provides high flexibility to create new workflows quickly. There isn't much work. We use it to track developers' and other IT personnel's time. Everybody enters all the tasks so we can create reports quickly. The integrations are fairly straightforward. The reporting and analytics feature considerably impacts our project management and decision-making process. I rate the impact an eight out of ten.

We had quite a lot of issues integrating BMC Remedy and Jira. They're different. A lot of information needs to be exchanged. The changes that need to be promoted from one on-site to another are challenging. It is easier to integrate Jira with other systems than BMC Remedy. The database has grown since we've been using the tool for 12 years. The performance and stability are visibly degrading since the database has been growing every year.

I have been using the solution for 12 years.

I rate the stability a six out of ten. We have a large database.

The demand is growing. Even though we put in additional and better hardware, the scalability is not what we would like it to be. I rate the scalability a four or five out of ten.

The deployment took a couple of months. We needed a team of five to ten people to deploy the product. I rate the ease of setup a nine out of ten.

I rate the pricing a seven out of ten. The tool is expensive.

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.

We don't use bug tracking in Jira. I haven't contacted support at all. I’m not responsible for maintaining the Jira deployment. My colleagues take care of it. I might recommend the solution depending on the size and purpose someone wants to use it for. If we don't have personnel to administer Jira, we will have to hire a relatively expensive company to do it. Overall, I rate the product a seven out of ten.

My company uses the product for the user storage it provides. The tool is also useful for requirements management and test management processes. The product is also useful to track the hours people in the company have spent on testing and test logging.

The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress. I also like the tool's ability to provide details phase-wise, allowing users to see how many tickets are in development and how many are in the testing process. It also helps users see how many tickets are ready to move to the production phase. The aforementioned areas of the tool are pretty frequently used.

Some of the customizations are definitely a little challenging. I depend on Zephyr to manage certain reporting aspects and deal with the challenges of customization. More than a thousand records are something that our company cannot retrieve, but with the administrator's permission, the limit can be increased. Some of the functionalities to increase the limit of retrieval, in case there are more than a thousand records, could have been included as a default feature since it would be helpful if I wanted to do some analysis or if I wanted to extract all the details when my limit is only a thousand records and then I have to search for another way to find and extract the details. If the aforementioned details of the issues in the product are addressed, then it would be great.

If there is a provision to increase the number of records retrieved, it would be really helpful. In the tool, only a predefined reporting is there, and it helps with some of the more customized reporting, like Power BI Report Builder, so the area of reporting can be enhanced and it can be really helpful.

I have been using Jira for two years. I am a user of the tool.

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

Scalability-wise, I rate the solution a nine out of ten. The product is always up and running in my company, and we have not experienced too much downtime in Jira, making it a very efficient tool.

More than 50 people use the product in my company.

I haven't had the opportunity to interact much with the product's technical support, but based on the inputs from the other members of my team, I can say that my company was able to get support from Jira whenever required. I rate the technical support a nine out of ten.

Positive

The product's initial setup phase was not very complex, as it is manageable.

The solution is deployed on the cloud.

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.

My company uses the product for planning tasks.

The product has played a major role in helping my company in the area of bug tracking. During the testing phases, be it SIT or UAT testing, if there were any issues, our company used to log the bug using Jira, and then we connect with the respective users, so we have a track of which particular bug and check to see if the bug is related to which user storage.

Jira helped our company's project management, analytics, and reporting parts. If you look at the analytical part, my company used to get the hours we have availed each of the user storage. When it comes to the user storage part, my company would like to see whether the hours we consumed were optimal or if it was over-consumed, which is information that we track with Jira. The tool is useful for tracking progress and seeing where my company stands when it comes to tickets. Each ticket might have a certain due date, which the company gets to see using Jira. Altogether, the tool helps users eventually understand the team's progress, the current sprint details, and how much of the team's capacity has been used. With Jira, my company gets to see the aforementioned details, so we were able to track it with the product's dashboard.

I am not used to using the product's integration capabilities with other solutions.

The product's user interface is good.

I recommend the product to others who plan to use it.

I rate the tool a nine 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.

I have managed various projects using Jira, including tasks for the government, the environmental sector, education, and donation applications. I have also worked on multiple websites for marketing and search engine optimization.

The most valuable feature of Jira for sprint planning is the timeline feature, which allows for better visualization and planning of releases. However, there are limitations compared to other tools like TFS, which offer more flexibility with features like user stories, epics, and initiatives without extra fees. Despite this, Jira's ease of adding user stories to sprints and connecting them to releases is very good.

Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist. In TFS, it is simpler to manage capacity and reassign tasks when necessary. Additionally, a feature in TFS automatically creates relevant tasks based on a code snippet linked to a user story, saving time and effort in task creation. This feature isn't available in Jira, which makes task management less streamlined.

I have been working with Jira for almost two years.

Jira is expensive.

I recommend Jira for its usability, especially for writing user stories and adjusting metrics, though it is expensive.

Jira has improved our team's productivity mainly through integrations, particularly with Slack. This integration helps keep track of changes made to user stories, providing alerts for any updates. 

I would recommend Jira for managing projects in agile environments, but certain features are necessary for better functionality, like improved capacity calculation and streamlined task creation. Additionally, Jira can be expensive, so essential tools like test planning should ideally be included in the standard subscription rather than requiring costly third-party plugins.

Overall, I would rate Jira as a seven out of ten.

I personally use Jira for project management and agile software development. I'm an information technology program manager and we are customers of Jira. 

We're a software development company and Jira is an essential element of our daily work. We wouldn't be able to function without it. 

Jira is a very comprehensive and flexible product. It's easy to set up, easy to learn, and is very user-friendly. If you're using the cloud version from Atlassian, there are no issues with maintenance or performance. I especially like the advanced planning features in the premium version and there are plenty of apps available if any functionality is missing.

The only complaint I have about Jira is that there is no field-level permission for the issues in the Jira cloud version. You can get an app for the server version, but the cloud version doesn't allow that type of functionality. For example, I write a user story that goes to the customer for approval. Once approved, I would want to be able to lock the description for that user story so it can't be changed, but I'm unable to do that. I can lock the whole story but not the description alone. It creates a problem because when I need to add the story to a sprint, I need to change the sprint number field. It can't be done because the whole issue is locked or lacks the properties to be edited.  

The other thing missing is a straight connection to the pipelines and the source control. I think it should be integrated with GitHub and other products that developers use. It's the lack of integration that's the main reason we are considering moving to Azure DevOps.

I've been using this solution for several years. 

I haven't had a single issue with Jira.

Jira is easily scalable to any level you want. Our company has 60 to 70 users working on multiple projects and we have a second installation specifically for one of our customers which has around 25 users. The users in our company have traditional roles; developers, business analysts, QA engineers, project managers and customers. We're using it constantly. 

Jira has a two-tier pricing system; a basic level and a premium level, which I think could be broken down a little more, but the pricing and billing are reasonable. You can add or remove users and they bill you dynamically month to month based on the number of users. It would be nice to have tiered pricing based on user numbers because, for large companies with hundreds of users, it's going to become expensive really quickly. It's acceptable for us and we have what we need.

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.

The product is very useful. As a program manager, I recommend it wholeheartedly. The cloud version is easy to set up, and there's no maintenance required. I haven't incurred any issues with performance or updates being applied incorrectly or any bugs. 

I rate the solution nine out of 10. 

We used it in my previous organization for project management, product management, and release management. In my current organization, where I started working a week ago, we are using Jira strictly for help-desk tickets. We are using DevOps for our release management. So, we've got DevOps, Jira, and some homegrown stuff, and I'm trying to figure out what's going to work best for this new organization.

I've used Jira and Confluence previously, and this is my first time using the help-desk ticketing system. It is cool and not a whole lot different than SolarWinds or Zendesk, except the appearance of it is more Jira.

We were using Microsoft OneNote for systems engineering and network engineering. It was being used for our documentation, environments, and services, and it was a nightmare. We transitioned everybody and copied everything into Confluence. We were then able to tag specific tickets to the notes, and there were links between what work was recently done and the most updated notes in Confluence.

The roadmap feature and the ability to integrate with Power BI are probably the most valuable features in it. It is a great solution. I absolutely love it. It is a tool that was designed for project management, and it has been awesome to work with it so far. I also love Confluence.

They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first.

It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that.

I have been using this solution for two years.

It has never gone down for me. It was always reliable, even from the mobile app.

It was fine. It seemed to integrate with all of our systems with ease. At my previous organization, there were probably 500 or 600 people using Jira. There were many different roles including product management, project management, VPs of IT and Ops, IT data services, developers, network engineers, systems engineers, and CBAs. It was a full scale of IT professionals.

At my current organization, where I started working a week ago, we are using Jira, but there are only a handful of people who are actually using it. It is strictly for help-desk tickets. I am trying to implement it and roll it out to the organization on a much larger scale, and I'm going to have to talk to them about pricing and other things. In this new organization, there are probably about 500 or 600 employees in total. Assuming I get the buy-in from everyone, which I don't think would be a problem, I would probably need at least a hundred licenses for users and then expand from there as needed.

I haven't interacted with their technical support, but I bet they would have been awesome.

I have used Smartsheet, MS Project, and Trello. Jira is more software-development-specific and a much easier tool to use.

In my previous organization, I believe its initial setup was complex. I was not at the administrative user level. I was given admin privileges for certain projects but not for the whole Jira. This is the first time I actually have admin privileges over all of Jira, and it was set up for me.

It probably took a few days. It would have also involved a lot of conversations and other stuff.

It would have been in-house. In terms of maintenance, it didn't seem to need maintenance from our side.

I would advise going with the entire Atlassian suite. Don't just use one aspect of Jira, unless you have a very specific need for using bits and pieces. Jira is better when Confluence and everything can be integrated, and you have source code management and all of that from the same software or platform.

I would rate Jira a ten out of ten. I love Jira. It has the ability to just do everything, and it is a one-stop shop for all of your IT software development needs.