Jira Reviews

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.

We are using Jira to manage our development sprints.

The most valuable feature is working with sprints and having the ability to create sprints. You can create and move onto the next one.

Also, for example, while I don't use a lot of plugins, when you have a ticket then all of the information you can put into it is centralized.

There are so many opportunities that you can create almost anything.

The sprint-related graphics need to be improved.

They are using story points for the sprint breakdown graphics. When you have five large stories with several story points, in the first week of the sprint, nothing gets done. This means that you have a flat line and then, in the end, all of the stories are done at the same time. So, we created all of the graphics but they were useless because it was just a horizontal line and then at the end of the sprint it dropped down to zero points. Basically, it was a square.

In the next release, I would like to see a good graph that takes into count what you put into your stories.

I have worked with Jira, on and off for four or five years. I last used it in April, a few months ago. I have always been working with the latest versions.

It's a stable solution.

Jira is scalable, but you will need knowledge of every team because in every organization you have several teams that work differently.

You need to understand and know how to scale and be prepared.

It doesn't require many people to maintain Jira. 

You can configure a lot yourself, depending on how many rights you get in the application.

If you have enough rights, you will have a lot of opportunities to configure it in the way you like.

I would recommend this solution to others who are interested in using Jira because you can do a lot with it. However, I think that as you start working, you should start small. Work with it and try to configure things that you really need. 

Involve the whole team in what you are going to use and how you're going to use it.

I would rate Jira an eight 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 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.

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.

Our primary use case for JIRA is for entering user stories into the login books.

The most valuable aspect of this solution is its ability to connect everything together. 

It also has good stability. 

I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. There shouldn't be the need to go through this. The process should be improved. 

It's not so good for testing.

I have been using JIRA for ten years. 

It has good stability until now. 

You can scale with it. 

We have around 35 users. 

I haven't needed their support. 

I previously worked with TFS.

There are a lot of similarities between the two. Especially in terms of working in the same field, tracking issues, and tracking bugs.

I would recommend JIRA to somebody considering it. I love working with it. 

I would rate it a seven out of ten. In the next release, they should make the process easier to be customized.

We are using Jira as our help desk solution, as well as for managing our software development efforts.

Jira has helped with respect to managing our software development, although it does not suit us well as a help desk.

The most valuable feature is managing software development.

The help desk and services management features are in need of improvement.

I have been using Jira for five years.

This is a stable product.

The scalability is fine. We have fifty people in the company who are using it.

I have not used the vendor's technical support.

The initial setup was done before I joined the company.

I am currently in the process of searching for better help desk management solutions.

My advice for anybody who is considering this solution is to ensure that it meets your requirements. For example, we have been trying to use it for help desk management, but have found that is not well suited for this task.

I would rate this solution an eight out of ten.

We use Jira primarily for Agile development and change management.

The most valuable feature is its flexibility. There is flexibility in the structure, lifecycle, and workflows that you want to work with.

The interface is user-friendly.

I would like to see more robust release management within the tool. We're not able to use it at this time because of compliance issues within our industry. At this point, I'm not confident that it can meet the requirements.

I have been using Jira for about two years.

This product has steadily improved since the time I started working with it.

I would rate this solution an eight out of ten.