Jira Reviews

We primarily use the solution for software management. 

I really like the linking and user stories, and the formatting on the solution. The formatting options and linking the user stories have been great. 

You can export the whole backlog if you want to - including your roadmap.

The initial setup is easier than the TFS.

The UX and useability os good, especially if you compare it to a solution such as TFS.

You can use it right away without too much of a tutorial. 

The solution is stable. 

The scalability is good.

I would suggest Jira makes the format compatible with Microsoft Word. Currently, when you copy and paste something from Jira, such as tables, it won't be the same when you copy it into a Word file. There are formatting issues. 

If you have 70 or 100 stories, it doesn't work to copy and paste or export each one individually. There needs to be better configuration at a categorization level. 

There needs to be a way to export a user story. 

By default, Jira is epic and story only. It would be ideal if there was a different categorization between the two. It would be nice if there was a third story option. 

There should be a plugin for test cases. 

If the solution doesn't have third-party plugins for some features, they should add it into the main offering to make it more complete. 

I don't have a lot of experience. I only have about four months of experience or something like that. It's not a huge amount of experience, however, I got familiar with the basic features of Jira over that time. The first two months might have been on a trial version.

The solution is stable most of the time. Only rarely are there some points where it's not stable. For example, when you view some issues, sometimes it gives an error. Then, after that, if you refresh or you open it at another time, it may work again.

The solution can scale. If a company wants to expand it, it can do so.

We have more than ten people on the solution. 

If you need to find answers, the community FAQs are pretty good. I've found issues in there in the past that have helped me troubleshoot. So far, I'm pretty satisfied with that aspect of support.

The initial setup is straightforward and simple. It's not difficult or complex. 

I don't deal with pricing, billing, or licensing. I can't speak to the exact cost of the solution. 

We likely pay a licensing fee as we have more than ten people using the solution, however, I can't say what the exact cost is. 

I have been researching the difference between Jira and TFS, to decide what is better for our team to use. I'm very familiar with Jira. However, some of my team members have experience with TFS. I'm trying to decide which management tool we will use in an upcoming project.

I have found that, with TFS, a lot of the features are built-in, however, with Jira, you are required to add in plugins. 

I'm a customer and an end-user.

I would rate the solution at an eight out of ten. For the most part, we have been satisfied with its capabilities. 

I would recommend the solution, however, I would warn that likely a company will also need to add many plugins in order to get the solution to do what they need it to.

Our primary use case is for project management, guiding the teams in our company. The solution allows you to create Scrum boards to deliver all the acquired stories within the Scrum Sprints. It also adapts to any other Jive methodology, like Kanban, and helps the creation of roadmaps for the software, production and implementation. We use it for day-to-day tasks, managing our stories, assigning tasks to different developers, and even integrating it with other system control tools to link the story's details. We are customers of Jira. 

The Jira user interface is really helpful because you can see the big picture regardless of what stage the task is at. You can define priorities and estimate times. If, for example, you're planning to move to Scrum, you need a project management tool; JIRA is perfect for that. It can also be used on personal projects because they offer a free plan with unlimited features to manage your project, define your backlog, and check the status of a project. 

The solution comes with multiple reporting charts so you can see the sprint burndown chart and other information. We previously had our own internal tools for Scrum, and moving to Jira was a total upgrade. There's no need to create new accounts for your users. You integrate company emails with an internal server, grant the user access and with their  company credentials, they can log into the platform. That's a pretty good feature. 

They could probably improve the integration with some of the automation tools and provide a specialized user interface suitable to their requirements. 

This is a very stable and reliable solution. The whole company uses it and we have around 500 employees. Our team adopted Jira recently but others in the company have been using it for a while. 

Jira is very scalable and allows for the integration with source control tools.

I haven't had to contact technical support. 

The initial setup was straightforward, we got access to it and started using it. They also provide you with documentation which helps if you are new to Scrum and new to the platform and features. 

There is an annual subscription fee based on the number of users. You can get a subscription for just 10 users, for small teams, and if you want more you can buy more. They have a standard and premium license. 

I would definitely recommend this product because it's scalable and easy to use. They provide best practice articles and quick start tutorials which are very helpful. If a new user has all the documentation, they can go from zero to hero very quickly.

I rate this solution a 10 out of 10.  

We primarily use the solution for collaboration purposes.

The solution has basically been problem-free so far.

Overall, we've found the product to be quite flexible.

The level of stability is quite good.

The product can scale if you need it to.

I'd like the solution to be more secure.

I've been using the solution for about six months at this point. It hasn't been that long. I've been using it for less than a year.

We've enjoyed the stability of the solution. It's good. It doesn't crash or freeze. There are no bugs or glitches. The performance is reliable.

The solution can scale quite well. If a company needs to expand it out, it can do so with relative ease. It's not a pronblem.

Not too many people use the solution in my organization. There are fewer than ten users right now.

We do not have any plans to continue to use the solution, let alone increasing usage.

I've never directly dealt with technical support. There was never a need to call. Therefore, I can't speak to how helpful or responsive they are. There was never an opportunity to interact.

We did not previously use another solution before implementing Jira.

I didn't handle any aspect of the installation, and therefore I can't speak to how easy or difficult the implementation was. I'm not sure how long the deployment itself took. I was just handed my login and I was good to go.

As I wasn't involved in the installation process, I can't speak to if a consultant or integrator was used. I have no knowledge of that being the case. 

I can't speak to how much a license costs or the process behind setting one up and renewing it. I just use the solution. I don't handle sales or billing.

I'm just a customer and an end-user. I don't have a business relationship with Jira.

It's my understanding that we are using the latest version of the solution, however, I am not 100% positive that is the case. I don't know the version number off-hand. I am also not sure which deployment model we are using and if it is deployed on cloud or on-premises.

I'd recommend the solution to other organizations.

I would rate the solution at an eight out of ten overall.

We are using the solution for project and defect management, and task tracking.

There could be some improvements in the project management and portfolio level features. I think they could bring more flavours of Agile to Jira, that would help.

I have been using the solution for approximately eight years.

We have found it to be very stable.

The solution is very scalable and flexible. It's one of the best products that we have been using. We currently have 80 users using the solution.

The configurations for the installation are very well documented on Jira sites. You can just go there and it has everything you need. The installation did not take much time, it was straight forward. 

We had one internal administrator do the implementation, the configurations are straightforward.

I would recommend this product to others. 

I rate Jire a nine out of ten.

I use it for project management and agile scrum projects. I am a manager, and I work with backlog tools and sprint plans. I only use Jira for backlogs, sprint reviews, and data reports. Our project manager is the person who is really working with Jira along with the team. We also have Confluence and Bitbucket. We use CloudBees and DevOps for the deployment of the environment.

It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories.

I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira.

I have been using Jira for almost one year.

I don't work too much with Jira. I use it only to see the reports, and I don't feel that there are many bugs. It is stable.

It is not too expensive. It is just comparative to other tools like Microsoft Teams.

I would recommend this solution. We are interested in migrating to Jira and using it as our internal tool for agile projects and for controlling the IT software development cycle for projects like consulting or API. It will be more used for agile projects. It is a good tool. We also have the latest version of Microsoft Teams, but it is limited. It is better to use Jira.

I would rate Jira a nine out of ten.

We primarily use the solution for product development efforts and documentation. We use Confluence as well for documentation.

Most of my work is keeping track of what's been going on and identifying what is blocking future work. What I like about this solution is you can create a consolidated customized dashboard out of your files to identify what's been going on and identify who has how much data assigned to them. You can begin to understand where roadblocks are and how to streamline efforts effectively. It's been helpful. 

The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything. While it should be a standard thing across the company to have labels created in certain way, the system should be able to pull up suggestions of labels that are close. 

The product could be more intuitive. 

If something isn't getting resolved, we generally aren't getting any alerts to warn us to this fact. We don't get any visibility on if something's been open for a few months even if it should have been closed after a few days. We need some sort of system that shows us items that are lagging.

I've been using the solution for about six months to a year or so. It hasn't been too long. Our company has been using it since they started doing development work.

In my experience, most of the time it's very stable. Sometimes we have a few bugs here and there in Jira. However, it doesn't affect our work in a very big way. It doesn't crash or freeze. It's reliable.

I'm not sure about the whole company, however, on my team, we use it extensively. We have around 30 to 35 people using it on this team. Obviously, they are using it on other teams as well, however, I don't know the count of each team.

In terms of scalability, we are able to add new users as needed, and that has never been a problem for us.

I've never had to reach out to technical support. I don't know how responsive or knowledgeable they are.

I didn't previously use another solution, Jira is the first product I've used for this purpose.

I actually was not involved in the initial process of the setup, therefore, I can't comment on the process. I have no idea as to if it was difficult or straightforward.

I'm not aware of any regular maintenance that is needed on the product.

I don't deal with the financial aspect of the product. I cannot comment on if it is overly expensive or not as I don't handle billing or payments.

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

I'm not sure of which version of the solution we are using.

I'd recommend others go ahead and try the trial version of the product. If, after that, it seems to fit your needs, a company should go ahead and implement it fully.

Overall, I would rate the solution nine 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.

Our primary use case for this solution is work management and task management.

We use this product quite extensively, and we're planning to roll out a module for the Accounts Department to be able to map manpower costs to project work, directly. That is something that we're working on right now.

Based on the flexibility that it offers us, we can adapt to different projects with different cycles. Based on whatever cycle we are working on for a particular project, we can configure the solution to suit us. This helps us to manage the work, essentially in one place, and we have visibility of all projects that are going on in the company.

The most valuable feature is the flexibility of the configuration, being able to configure it to suit your own needs.

The plugin management needs a lot of work. Sometimes you have issues with plugins and it stumps the vendors, as well as the Atlassian support.

I think that more extensive reporting would be very good because sometimes it is a hassle for us.

It is pretty stable. I would give it a ninety-five.

In terms of stability, it is pretty impressive and I would give it ninety-five. We have not had any load issues.

We currently have between twenty-five and thirty users, whose roles range from Software Developer to Chief Executive Officer.

I would rate the solution's technical support an eight out of ten. 

I have used a couple of solutions, but I have used this one for my entire career in working with different teams. I have had to integrate my own solution as well, but the majority of my work has been using this product.

I have worked with both the hosted application and the cloud version. For the cloud, the initial setup is very easy. You can do it in basically two minutes and you're out but for the server, the setup entails a lot more.

This is quite understandable because you're going to be managing it by yourself, onsite. For the Cloud, it's pretty straightforward, but if it's the server version then you need a lot more focus and experience to be able to configure it correctly.

The last time I installed a server instance we had to do it overnight and it took me between four and six hours.

The deployment was done in-house.

There is no maintenance required for the cloud version.

I would say that we have seen ROI with this solution. When we are looking for some sort of information, it just makes our lives much easier because we are able to do things without having to talk to anybody. You know exactly what is going on. It limits personal interaction but helps us to get our jobs done quickly.

Licensing is on a monthly basis, and it is based on what you use. There is a base cost and then as you include other items, the cost rises. Our last payment was perhaps $1600, which includes both user licenses and add-ons.

There are no additional costs beyond the licensing fees, and it covers support.

Before choosing this solution we evaluated SmartShift for work management, and we also tried Trello.

My advice for anyone who is implementing this solution is to ensure that your in-house processes are clear. Things have to be clear, as much as flexible, because if it is not correctly configured then it could just be a mess. So, you have to be very clear on what your processes are in-house, and then based on that you can translate them into Jira.

Knowing in advance what kind of information you're looking for from Jira will help you in being able to set it up correctly.

I would rate this solution an eight out of ten.