Jira Reviews

The solution's most valuable aspect is its workflow sensibility.

The user and group management could be improved in a big way. There really are a lot of administrative areas that require a lot of screens which could be improved in many ways.

A lot of the user interface could be updated.

Technical support is lackluster. It could be improved.

They need to address a lot of the requests that people have had over the last 10 years. Instead, they rely on third-party tools to provide these features. They don't seem to understand what it is their clients really need and instead just assume a plug-in can be made for whatever the purpose is.

I've been using Jira for ten years. It's been a decade now since I first started working on the system.

The solution is extremely stable. There aren't bugs and glitches. It doesn't crash or freeze. It's quite reliable.

The solution is absolutely scalable. If an organization needs to scale up, they can do so easily.

Technical support is pretty bad. They rely on partner companies for support and don't really have any of their own internal teams that can help.

The initial setup is not straightforward. It's quite complex. However, you do tend to get used to the process after a while.

The solution is quite expensive. I'm not sure of the exact pricing, however, I know it's not cheap.

We're an Atlassian partner.

I'm actually using various versions of the solution. I stick with versions seven and eight, mostly.

I'd rate the solution seven out of ten.

• Great user interface - it is light and very user friendly
• Web technologies - no need to install any local ("thick") clients on PC, just web browser
• JIRA is very customizable and has a modular structure - this is very important, when an organization has often changing workflows
• Powerful reporting and filtering systems
• Time tracking and workloging
• Fully customizable desktops

I advised my friend to introduce JIRA at his organization and I helped him with this. Here are some results after about two months:

• Employees stopped to write on colourful stickers and leave its at their monitors
• My friend and his manager can see what each employee is doing and find lazies
• Each project participant began to think before writing (earlier someone could say something but after some days his/he worlds were forgotten, or he/she might say that he/she didn't say that, etc);
• Employees started to plan their time and try to work faster and better
• Customers of the organization now can create tickets and requests via JIRA, no phone calls, no email conversations. The result - most of requests from customers are processed faster.
• A customer can see the time tracking of his tickets, so he can plan future requests and calculate current and future payments (and all that without phone calls).

There are some little bugs and features which need to be resolved, but they're not so critical. I think JIRA should have features like drafts of issues as Confluence has drafts of pages.

I've used Atlassian products for about 8 years.

Earlier versions of JIRA were more difficult to deploy, but current versions are deployed very easily. I have good knowledge of Linux, and I have never experienced difficulties with JIRA installations, even the early versions.

No

No

I used many other solutions before but my manager chose JIRA. I started using JIRA about 8 years ago and the choice was made by my manager as well. Now when I start my own project, the first thing I do is starting to configure JIRA to the project's requirements and after that I can start my project.

It was straightforward.

My first setup was just for 10 users with a license of $10.

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

The main thing you should think about before you start implementing JIRA is ask yourself - "What result do I want to get from the solution? What problems do I have? What problems do my employees have? You should dream about your ideal team of employees and you must make your dreams a reality, and JIRA will help you with it".

Jira is used for issue tracking and defining the development pipeline. It's helpful to define when a project is done and track a task as it moves through different stages. The deployment type varies based on the customer's environment. We sometimes connect to the client's setup, which can be in the cloud or on-premise. 

I like that Jira allows you to customize the flow for an agile process and adapt it to your own flow.

We've used Jira for around 10 years.

We evaluated Jira for security and stability, and everything went well. 

Jira performs well and scales up enough to meet our needs. We probably have about 200 users, so we don't need more than what it offers. 

We used a solution called Mantis a long time ago. We're a software outsourcing company, so we adapt to our clients' setup. Plus, Jira serves our needs well, so it made sense for us to work with that. We don't recommend anything else. We use Azure DevOps, Jira, and Confluence on our projects. If it's not in Microsoft, then it's Jira and Confluence.

Deployment isn't something I handle personally. Our DevOps department does that, or it's installed by the client, so I'm not dealing with it either way. One engineer is enough to deploy.

I don't know the price of all the setups. Our clients pay for the setup, so our Jira users are covered by them. Of course, the price could always be cheaper.

I rate Jira nine out of 10.

Hybrid Cloud

We are using Jira for task management.

The solution has helped our organization be organized. We are able to create sprints in Jira to manage projects and tasks according to capacity and time.

Jira can track projects, time management of assignments, and keep everything on schedule. The performance of the solution is good.

Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects.

I have been using Jira for approximately two years.

The stability of Jira is good.

We never faced any kind of issue in the scalability of Jira.

In my department, we have approximately 200 people using the solution. There could be more people using the solution in my organization but I am not aware.

I use Jira every day.

I have contacted the support from Jira a few times. They have been good in my experience.

I have not used another solution previously.

The implementation difficulty of Jira depends on what tools you need. In the company I am working for, it was not difficult because we have a small team and we were not using many tools.

I would recommend this solution to others if they cannot find a better one.

If someone wants to implement Jira, then it should be fully transitioned. In the beginning for us, it was not implemented one hundred percent, which caused some hassles for the transition for everyone.

We have benefited from the use of Jira has improved the way we operate. You can see what everyone is doing in your team and you can check and get updates on progress.

I rate Jira a seven out of ten.

Public Cloud

We use it for project organization, workflow, and team collaboration. 

I like it for team collaboration and task management. I also like its analytics and dashboards.

It is easy to use. Our junior people find it easy to create tasks in Jira. It is intuitive if you've been using similar products.

Their support should be improved. They should be faster and more knowledgeable.

In Jira Cloud, integration with Excel is missing. Previously, I could import our Excel files into Jira, and I could also download a big Jira report in the Excel format, but now, it needs to be manipulated after that, which is not good. It looks like they've done that on purpose, but I don't understand the reason for it.

I have been using this solution for 10 years. I have used it in different companies.

It seems stable to me. 

It is scalable. It can cover many projects and a lot of job delegations.

We are a company of 2,000 people, but we all don't use Jira. All IT departments use Jira and Confluence together. They are always paired together because documentation is important.

Their support, in general, could be better. In my recent experience, people who were allocated were slow, and they didn't have the knowledge. They ask you to read the help and documentation about an issue and do self-service.

We also have Teams because it is given to us, but we don't use it because it doesn't have that richness, and it lacks the features that people need. It's very light for task management.

For me, it is straightforward.

We have a corporate license, and it is probably based on the number of people.

I would recommend this solution. It gives you the best if you investigate a little bit and maximize your use by using all the features.

I would rate it an eight out of 10 because of the support.

Public Cloud

I'm quite happy with it. 

The solution works well and does what it needs to do. It has been reliable.

The pricing of the product is fine.

We've never had an issue with technical support. We're happy with them.

I don't really have any areas for improvement. It works very well for what it is. I don't have any suggestions.

We'd like to see Jira have more integration with a development ID.

I've used Jira for six years at this point. It's been a while now. I don't use it as much as I used to, however, I still use it.

The solution works well for us. We don't have any issues with performance or reliability. There are no bugs or glitches. it doesn't crash or freeze. 

Technical support has been fine. We are satisfied with their level of attention and have been happy with them overall. 

We currently use Azure Boards, which is kind of a competitor to Jira, and one of the main reasons why is that it's more integrated with the development life cycle.

The pricing so far has been okay. I don't have much to comment on.

We're just a customer and an end-user.

I'd rate it as an eight out of ten. 

On-premises

We primarily use the solution for all issue reporting. The business uses it and we use it in IT as well. Any issue, anything from the help desk to software issues use Jira. It can house test plans, test sets, test executions, and provide some reporting. It's the reporting that's important for us.

The product has formalized the workflow process for reporting tracking and stacking and processing issues. It's also added some formal approvals, just for the purpose of formalization of a process workflow.

If you're using it in an agile shop, the traceability between epic story's test case defects is very helpful. 

I like that all of the team members on an agile team can use it. No one is in a separate application.

The stability is good.

The product can scale, so long as you have storage.

The reporting needs to be better. Being able to do some test management would be useful. In the tool, it would be ideal if they could give you some out-of-the-box reports for things like requirement coverage and regression and things of that nature.

I've used the solution off and on for about four years. I used it when it first came out to do some evaluation and we implemented it at a startup. That was when it first started. I've probably only really used it for about eight months on a daily basis.

We have had no downtime, and therefore I don't have anything to say that would be negative. It seems to be quite stable. There are no bugs or glitches and it doesn't crash or freeze.

As long as a company has the money for storage, it's scalable to any size. A small company can use it or an enterprise-level company can use it. It works for both.

Currently, we have less than 1,000 users in our organization using the solution.

Jira is extensively used in our organization.

We do plan to increase usage as well. The company purchased it so that it would be scalable. There's not a solid plan right now to add measurable users or increase the size, however, we know that it's available and that's what we were looking for - something that is scalable. The plans are to grow and as that growth happens, either organically, or via the purchase of other financial entities, we can grow the size of the database application and the number of the users.

I did not personally use technical support. I have worked several months with the people who have, and they say that the support is very good.

If the company used something previous to Jira, it was before my time. It possibly could have been Sharepoint, however, I was not with the company at that time.

The solution was implemented before I came to the company.

That said, my understanding is that the company tried to use as much out-of-the-box functionality as possible and it was quite an effort. They spent quite a lot of time formalizing workflows and things of that nature. In the end, it was very well thought out.

We do have a team for maintenance and what takes the most time with any upgrade is going through the changes, the enhancements, the defect fixes, and things like that. The actual time that it takes to physically update it is pretty minimal. However, going through the documentation and meeting with the team to make sure that we have testing covered prior to upgrading is work. We have a test environment prior to pushing it to production. That's what really takes time. It's not the physical update. An update might take two and a half hours and there's a lot of data in there.

My understanding is the company used professional services from Jira and also got some training and stuff of that nature.

We're just customers and end-users.

We just upgraded the solution. We are on the latest version.

I'd advise potential users to make sure that they talk to the people who are going to be testing and make sure that they know, what metrics they need before they pick a tool, any tool - even if it isn't Jira.

I'd rate the solution at an eight out of ten.

Private Cloud

Microsoft Azure

The way it interfaces with Bitbucket and other things like that is valuable. Reporting and being able to link various issues or stories together are also valuable. We call them stories, and they're general reports.

I never had an issue with it at all. Everything I needed to do was always there. Everything is cool.

It should have Behavior Driven Development (BDD). There should be an option to add macros to help with that. A lot of people are using it now, and it would be nice if there was a way in there to be able to generate the BDD of commands whenever you're creating a story.

I have been using this solution for probably 8 to 10 years. I have used it at different companies. Cloud is the way they had it set up.

There were probably about 600 users, and they were from top management and all the way down to the testers. So, pretty much everybody used it.

I would rate it at least a 9 out of 10. That's because I never had any issues with it. It always did what I needed it to do.

Public Cloud