Jira Reviews

We use Jira product in the organization to automate the software development life cycle.

It's a very flexible product.

We can change the workflows as much as we need and we've done that already. 

The workflows are very easy to handle as far as scalability goes.

If there is a feature or a workflow feature, that is required and it's not available out of the box from Jira, from Atlassian, we have the marketplace buy from. There are a number of add-ons that we use. We have maybe 20 to 25 that fill in any gaps in the system itself.

The user interface is very detailed right now. It could be simplified if they consider targeting the user experience. Right now, on the screen pre-design, the amount of information on the screen is very high. The distribution is good, however, the presentation itself looks very technical. They should work to streamline the UI to make it better for users to digest the information.

I've been dealing with the solution for two years now.

The solution is very stable. We haven't had issues with bugs or glitches. It doesn't crash or freeze on us. It's quite good.

The solution is scalable in terms of the number of users and the number of features. The features we are using are mostly out of the box, however, we have added product management features and code delivered with the integration features. We also have added test management tools or add-ons to it including reporting and dashboarding as well. You can really grow it out and add as many plug-in apps and features as you want.

Currently, we have 500 users that interact with Jira within our organization.

We have good internal technical support for Jira in the organization and we use the Atlassian technical support only when needed. Thus far, we are quite satisfied with the level of support we receive.

I cannot give too much information about the installation, as we're similar to a consultant, and I don't want to get into too many details. As the installation engine, we took two days straight to deploy it and that is with the implementation.

For deployment, you don't need a huge team. We did it with two technical personnel. They are consultant level system administrators.

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

We're using the latest version minus one, due to the fact that it was installed year. That upgrade was last year and it is my understanding that there is another version coming up.

I'd recommend this solution to other companies.

The product is very scalable and it's very flexible to match any organization, however, the trick to using Jira effectively is that there should be a business process documented in place before using it straight. The mistake that many people do is they consider the tool as the base and they configure their processes according to this. If they work the other way around and have a great process between all cycles, and then implement that process on Jira, it's very beneficial.

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

Virtually every day we have our daily scrum. Our team gathers around the board, which has all the columns showing where the tasks are standing: requested, planning, ready-coding, review, etc. Together, we view one task after the other and update the statuses. It's really a focal point of the team to know where the work stands, and what's the progress of the work since the last time we checked.

Within my company, there are roughly 25 employees using this solution. We have a scrum master, who's the most knowledgeable person on the tool. usually, they're the ones organizing the tasks, creating new tasks, and then creating the report at the end of the sprint or the quarter. They're the person who's creating the reports, using the more advanced features. That's the scrum master.

There are the developers, including me as a tech lead. There's the tester. There are managers — once in a while we have to present them with some reports and statistics, so they know how much work is being achieved, but they don't have in-depth knowledge of the tool. It's really an internal tool, so the customer is not involved.

We're not expanding much at the moment. We've been expanding in the past year, but now things have slowed down a little bit due to COVID-19.

With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board. Nothing gets forgotten — it forces the team to make a decision on every little task that is planned.

The way we can quickly see in which state a task stands — with everything classified by columns. It's easy to know who is taking care of what. For instance, if I want to know how busy the person in charge of QA is, I can easily see what staff members are working for him via a little face icon or a tower. I can see who is responsible for what tasks. The board gives you a quick summary of the workload of everybody on the team.

When a task is completed, it disappears and I don't know how to find it. If I want to go back in history to review an old task that we completed, I cannot find it. Unless you remember a keyword or a task number, it can be very difficult to find old tasks.

Sometimes, in the display, there is an overload of information that makes it very difficult to read. If there's too much information, it defeats the purpose. You have to reach a balance, and I think at the moment, there can be too much information.

Sometimes the interface is too crowded. It seems like the default option when you open a task is that everything is open and all of the menus are deployed.

There needs to be easier integration with third-parties — personally, this is the biggest issue for me.

I have been using Jira extensively for one year.

Atlassian tools from the Atlassian suite are all linked together. We use GitLab. We wanted to integrate GitLab with Jira because whenever we create a branch in GitLab, for a repository, we create a branch to develop a feature or to fix a bug. Once the work is done, we have to merge that back into the master branch. When we do the merge, we name the merge and we enter a reference to a Jira issue.

It's easy after that. The person who's taking care of and viewing the merge requests can just click somewhere on a piece of information in the merge request, and it brings you to Jira, to the associated tasks. Usually, for each task, we end up creating a branch; it gets reviewed and merged back into the master. Once the review is done, it's ready to be tested.

That's our work procedure. Basically, the two tools — GitLab and Jira — need to be integrated with each other, but at the moment, there is a bug and It doesn't work. IT reported that problem to Jira or GitLab, but we have not heard back. 

There is a problem when it comes to integrating Jira with other tools, or other tools with Jira, there seems to be a weakness there.

Adding more users is not a problem. We haven't tried to add a third-party or to integrate with a third-party, so I can't comment on that. 

We don't tend to use Jira outside of its purpose at the moment. It's hard to answer this because we just add or remove users; we're not trying to upscale it to a higher scope or anything.

I go through IT for technical support. Except for that problem I mentioned, the integration between GitLab and Jira, we tend to find the answers pretty quickly.

Jira offers good technical support.

I didn't help with the initial set up myself. Since we have web access, you don't have to install anything. It was already installed when I joined the company.

Our IT team handles all maintenance-related issues. They don't necessarily know all the menus of Jira, all its capabilities, but they know how to deploy it.

Have a training session before you begin using it. That tool is good for teamwork, but it doesn't replace a face-to-face discussion. Among yourselves and your teams, establish some conventions as to how you will describe your tasks — what criteria will be acceptable? Include a section for requirements, have a section dedicated to discovering your setup because the tool has its limits. It helps you organize your work, but it doesn't replace the self-discipline of the developers to stick to some team conventions — that's also really helpful to get the full benefits of that tool.

One of the main advantages is that everything becomes visible when you use this tool. When your work is done in full daylight, it's difficult at the beginning because you feel like everybody's looking at what you do — it's all visible. They can access the information through JIRA, but at the same time, you're not going to get stuck too long in your corner. The drawback is that you feel more like you are being spied on. It feels like you're working in an aquarium. Everything you do is visible. But at the same time, you're not going to get stuck on your own. Without this tool, it's easy to get stuck on your own.

There's room for improvement. Sometimes the window is too crowded and the integration capabilities need to be improved. Overall, on a scale from one to ten, I would give Jira a rating of eight.

We have a service desk for customers. We have the whole flow from customer feedback throughout, committing with a relation in the code in Bitbucket.

We have the tracking and tracing, including all tracking of the issues all the way from the customer throughout the JIRA prioritization in backlogs and sprint planning and connecting those through the actual code commit in BItBucket. It's all done through JIRA to the service desk issue and back again to the customer. The entire ecosystem is quite connected.

The best features depend a bit on the project going on. We have some project managers for the Classic Project setup and all the features that come along with the Classic Projects. 

From my point of view, the NextGen Project in the cloud solution is really easy to start up with and it's quite flexible in how you put up columns and move issues and tickets throughout the status and columns that you put up. 

It's really flexible. From the Atlassian point of view, I can see they are moving towards more Next-Gen Project handling. The features from the Classical Projects are being continuously rolled out towards Next-Gen Projects. Of course, there's still lots of ground to cover.

It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it. There's some approval function or a step via the Atlassian team to be able to actually endorse your apps throughout their marketplace. However, it's very smart to have collaboration between the company and third parties. Whatever functionality is lacking, there's most likely an app for it. 

I've seen some updates and subscriptions where you can get newsfeeds if you subscribe. They are focused on making the solution as responsive as possible. For instance, they have enabled some features called Project Archiving. If you're done with some project work, you could choose to archive everything related to it. Therefore, it won't be upfront taking resources from your solution, however, you'd still have access to it in the future.

Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed. It's my understanding that the reason they started doing the Next-Gen and changing up the whole dual-end functionality is probably because of how heavy and big everything was getting. It had gotten pretty complex within the Classical Projects. 

It's quite time-consuming picking up the Classical Projects. They've gotten quite heavy and it's hard to use them in a productive way. There are just so many settings and possibilities. It's very complex and time-consuming, however, on the other hand, it's got everything you need in terms of functionality.

We've been using the solution for a year and a half now. It hasn't been too long so far.

The solution is quite stable. We haven't faced any stability issues.

The solution is quite scalable. They also allow you to archive old projects so that they don't take up space on your product, and that can help you scale. You might need a specific kind of subscription in order to archive, however.

I don't really have much experience with the technical support team at JIRA. I've been reading the community tickets mostly. Most of what I've been curious about, I've been able to find the answer myself via the community or the WIKI. 

You can communicate with other users, which is really smart. It allows you to discuss best practices effectively. At the same time, I would guess that some of the users there would be actual Atlassian employees that are commenting and guiding. Overall, the community space is quite helpful. Therefore, I haven't really had any issues or tickets or any need to connect with a technical team in Atlassian.

One of my colleagues actually had an issue when a new user was invited before he had opened his 365 email. He had not logged in to the email account. Therefore, when the invitation was sent from Atlassian or from JIRA, I can't remember exactly which module, but then there was feedback that this was not an active email account, which made Atlassian revoke the whole user. Then, when he actually logged into 365, he wasn't able to connect to JIRA due to the fact that the email had been marked as expired or not an active email. He sent the request to Atlassian and they opened up a ticket and everything was fine within a couple of hours. It was really quick. That I think is probably the only dialogue we've had with the technical support in Atlassian and it was pretty positive. I'd say overall we're quite satisfied with their level of support.

The initial setup's level of complexity varies. If you use the Next-Gen Project, you can get it up and running in, I would say, five minutes. That part's quite easy.

You can also just subscribe and you can get the free version. I really like that kind of subscription that you can start with quite a few features available. You can get it started for up to five to 10 users without any cost. Then, when you start getting the ball rolling or the projects rolling, you have to actually insert your credit cards to both get features unlocked, and also to add more people to the projects and to the solution. 

If you want to, you can add on quite a lot of features and connect with the apps from the Atlassian marketplace. That's also a really nice possibility. You can just click, add apps and it takes about 30 seconds. Then you have added functionality injected to your solution.

I would guess we are using the latest version of the solution as we're using the cloud solution. I'm guessing that it's continuously updated automatically.

I'd advise others to consider the solution. However, It depends on what they're trying to achieve. There are a lot of easier project management tools like Monday.com, for instance. It's a lot easier to get up and running.

If your vision is to become a larger software development company, monday.com might be something that is usable for project managers. However, it wouldn't be a good tool, at least how I've seen it, to connect everything together as we're able to do in the JIRA cloud with all the connecting apps. I would guess we would be able to integrate Monday to JIRA or something like that.

It's really easy to get JIRA connected to Confluence and Bitbucket and to have the service desk as well. That way, everything is in one place. Again, it depends, on based on where you're heading. If the company is looking for easy project management, there's a lot of tools that would be just as good as the JIRA. If you're looking to distributing the teams and connecting a whole ecosystem, then definitely JIRA is a good pick.

I'd rate the solution seven out of ten.

In terms of using Jira, I was more on the user side and not really acting as, for example, service desk or support for the Jira installation. That was not my part of the project. I was more tasked with setting up the infrastructure from the architecture point of view. We needed a ticketing system and we need a planning system and the team that was responsible for the tools was installing and providing them with the workflow that we needed.

The solution is pretty flexible. I have worked in different projects using different features. From agile to just normal project management and task management. It's got a lot of great features. 

If we're talking specifically about project management, the solution is pretty nice. There are a bunch of modules and plugins and add-ons that you can use if you need to.

The test management aspect of Jira is pretty pure. They have a lot of great plugins that really expand your options.

There's always room for improvement, however, it depends on how you intend to use the solution. It's hard to pinpoint exact features that are lacking as the solution is quite vast.

From the project management perspective, I would say there are a lot of different issues that could be tweaked. There can be small improvements with traceability, for example.

I have no idea how long I've been working with the product at this point. It's probably been about ten years or so.

The pricing is fair. Right now, I'm using the solution for my small projects. For example, I'm using the Jira Cloud and Confluence Cloud, which are pretty nice. For small teams, it's a very, very interesting option.

We're just a customer.

I'd advise, for those users who don't need an enterprise-level environment, that they go for a cloud deployment. For others, they don't really have a choice. They will have to follow up with enterprise security and other protocols. There are not that many options, I would say. 

I have learned that Jira, starting in 2024, will not be available as a server installation anymore. Soon there won't be any options at all. It will be the cloud or nothing. 

Overall, I'd rate the solution ten out of ten. It's a very good product.

For small teams, the cloud works well. You can do basically whatever you want there, so it's fine. It's also not cost intensive if you're talking about using it for small teams.

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 it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there. With that, I am able to create a kind of gauge, estimate, and forecast our capacity planning for the next two weeks. We use it to create peer reports.

A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time. So I have to do multiple exports to just create the sub-tasks and sub-tasks are not being reported. If I wanted to export this and recreate this in another platform like Azure DevOps, I would have a problem right now.

I have been using Jira for four months. 

The support person I contacted was not skilled enough to provide me the answer so it's up in the air.I'm just doing multiple exports. 

Jira as it is, is a very nice tool. For capacity planning and resourcing, I think it is not built for this and we are trying to make use of it in that area.

I would rate Jira a seven out of ten.

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.

I am a consultant, and we have some customers with projects who use Jira.

We have customers with different Jira installations because there are so many vendors. It is mostly used as a bug tracking system with tickets, issues and tags.

The feature that I have found most valuable is that it is a quite powerful user tracking system. Also, we use it to print tasks for planning so you can also see what's happening in the system and follow the tickets.

In terms of what could be improved, there is not much I don't like. It is a little bit faster but with Firefox it can be slow, but that is also the case with many other tools as well. It has quite a lot of options and fields, so I'm not too familiar with them all. That makes it a bit trickier. It could be a little bit easier, it is not that simple or straightforward. 

The tool itself is so powerful and the customer's expectation is very high because you have so many things you can do with it. That can make it a little non-user friendly.

I would want to see Jira include some improvements, like drag and drop and color, to make it more straightforward. If you compare it to Microsoft or Octane, they have good features that I would like to see in Jira as well.

Overall, Jira is a little bit old fashioned, it could be more user friendly.

They should make it simpler, to just be able to do some functions, whereas now it takes longer. There are too many clicks.

I have been using Jira for around 15 years or so, but not all the time.

The stability is fine. We have some issue now with our customers, it could be due to the network or other issues, I don't know if it is because of Jira itself. We have quite a complex environment and system for our customers. At the moment we have several tools and different systems. We have some issues with downtime but I am not sure why.

My advice to anyone thinking about Jira is that it would be wise to at least find out the most crucial functions that you need in the product, what features are most important, determine how the project will use Jira, and the most important thing is to have some kind of user training plan because the tool is so complex and flexible that you can use it in many, many different ways. 

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

I would give it a nine because of course it needs some improvements. For example, the usability and its speed.