Jira Reviews

We use Jira for project management for the development teams. Additionally, we do backtracking and managing the backlog but it is more of a development team tool.

There are a lot of plugins in Jira and we purchase the ones we need.

Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too.

I have used Jira for approximately 10 years.

We have never had an issue with the stability of the solution.

We have approximately 400 people using the solution in my organization.

The support from Jira is good.

The configuration can be complicated, there are a lot of options.

We have a technical team that does the implementation and maintenance of the solutuon.

The basic price of Jira is reasonable, but for each plugin, we have to keep paying more. When you add it all up, it can be expensive. The main problem we face is we are forced to purchases plugin licenses for users who are not going to use them. For example, we have Jira licenses for approximately 450 people but if we only want a purchase a plugin for few people it is mandatory to buy the license for the 450 people who have Jira licensees. This is a problem because sometimes we need plugins for the product manager or for people in charge of the report, not everyone. For us, it can be very expensive in the end, they should alter this policy to allow plugins for only a set number of licenses.

My advice to those wanting to implement Jira is to have a lot of support. In our company, we started out small with only approximately 25 people and then we expanded quickly. Jira can be complex to manage, and it is better to have some advice or some people to help with the implementation.

I rate Jira an eight out of ten.

We use Jira for enterprise planning.

We like team collaboration and cross-functional collaboration.

The history with Jira is that it is a bit complex for many users.

There are too many features.

The user interface is complex.

I have been working with Jira for five years.

We are migrating to the latest version.

Jira is pretty stable.

It is scalable enough.

We have 1,000 users in our organization who are using Jira.

We plan to increase our usage.

Before Jira, we did not use any other solutions.

The initial setup is straightforward, nothing out of the norm.

We had a perpetual license but have changed to a subscription.

We are not satisfied with the pricing. It has become more expensive.

We would prefer it to be cheaper.

We evaluated other solutions before choosing Jira. We chose Jira because it is widely used.

I would rate Jira an eight out of ten.

I am currently using Jira for project management purposes, such as tracking the team and opening tickets. I am an admin in my project. When we start a new project, I open a new story in Jira for that project, and I open sub-tasks for that project. From there, I create backlogs. Our team is responsible for those backlogs. I have previously also used Jira for designing workflows for our enterprise.

It is helpful for tracking efforts for our projects. We have around 20 mandate projects, and Jira helps us to see how much effort goes into which feature and which team members have put effort into a project. It helps in anticipating the efforts for the next projects.

The ability to design your own workflows is a great feature.

The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me.

Understanding the workflows can be a little bit difficult. For example, if you don't know the workflow well and you get an error, which is not a technical error, you won't be able to find the reason for that error.

I have been using Jira for the last 15 months.

There is no problem with its stability.

Its scalability is good. Too many people use Jira, and there is no problem with its scalability. It is a scalable product.

Our Jira team has five people, and our company has about 1,500 people who use Jira for tracking efforts. We are using it almost every week, and we don't plan to increase or decrease its usage.

We take support from the Jira team in our company. I didn't take support from Atlassian.

I have been with this company for about three years, and they were using Jira when I came here.

I didn't deploy Jira. We have a dedicated Jira team in our enterprise. There are five people on that team. This team supports two Jiras. They also support SoftTech Jira. It is used by about 20,000 people.

I don't remember the deployment time. The upgrade took 8 to 10 hours. We do maintenance frequently because when business processes change, many changes are required in the backend. Jira team takes care of the maintenance.

I would rate Jira an eight out of 10.

I work for an insurance company that has developers who need to be tracked. We're working on converting the spreadsheet into a Kanban flow environment. I'm the program manager/master. 

The solution is very powerful, has many good features, in particular a good reporting capability. I like many of the features, and I have the benefit of having a very skilled Jira administrator helping me out because I'm a PM. 

The solution is not as intuitive as it should be and you have to play around with the environment quite a bit before you get a handle on how things work. One of the issues is that it's usual for a ticket to have a primary developer on it and other people supporting, but that's not possible in Jira. They have a very thick policy and a ticket can only have one assigning, although it may be possible to do it as a number coding, I'm not sure. I'd like to see the solution include a feature whereby you can link stories visually, to explicitly show the connection between a user story and a task. 

I've been using Jira for several years. 

Scalability of the solution seems fine.

Technical support could be improved. When you submit a ticket, it can take two or three rounds before you get what you're looking for. I send the ticket and receive an irrelevant response, which doesn't help. You can go backwards and forwards with them and never get there which is very frustrating. I'm not sure if the user community is that helpful. I've submitted two questions but haven't yet received a response. 

The initial setup was quite complex. 

The solution is fairly good at doing a lot of things, and is potentially very good, but it takes some getting up to speed on. I've used a product called Kanban Flow, and that's very intuitive, very easy to use. Jira seems to be more complicated and requires having specialists on board so that if you have a problem, you can get help immediately without having to go through the ordeal of submitting a ticket and waiting two or three days to get a response, which may not be helpful at all. 

I rate this solution a five out of 10. 

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.

I believe we are using the latest on-premises version. 

Confluence, not Jira, is the most convenient feature with Atlassian. We use the product for knowledge management, the use of creating or documenting knowledge into a knowledge base.

I would like to have a future-proof idea of the cost and the roadmap for my class. This is in light of the fact that they are switching things up, promoting the cloud service and mixing different support levels.

The CMDB and knowledge platforms that are in the background of the ticketing tool should also be addressed. 

I have been using Jira for five years. 

When it comes to the question of stability, this depends wholly on the amount of resources provided to the virtual servers, since we make on-premises use. 

We have internal Atlassian experts, so it is tough for me to comment on the technical support.

The price of the solution could be lower.

We are currently in the initial stages of contemplating a switch from Jira. 

My advice is to work closely with Atlassian to make sure that all the designs are future-proof.

It is tough for me to Rate the solution. There are features needing improvement, but also many good things about Atlassian. As such, I rate Jira as a seven out of ten.

We are using it for service management, change management, project management, and tracking the changes.

It is user-friendly, and you can manage your project according to the methodology you want. It is also easy to configure.

The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough.

So far, I've only used the project management parts. We are examining resource planning and sample plugins for the product. From my point of view, resource planning is a little bit hard to link with project management. Sample plugins are another part of the system, and we need to link it with project management in the BigPicture screen, which is a little bit hard. It would be valuable for us if we can do resource planning in BigPicture as well. Currently, it is another plugin, and you can only plan based on the people and not projects, and you cannot link it, as far as I know.

My company has been using it since the beginning of this year. It has been around six months. I have been using it for three weeks.

It is stable, and everyone generally looks satisfied.

We are trying to settle the project management part and widen it to all countries in our company. There will be many users.

We are working with a consulting company. Technically, we are okay because all of us are using it now, and there is no problem. We just need to see more details of some of the modules of Jira.

For its implementation and deployment, they have been working for one year.

Jira is a big platform, and you can use staff management, project management, and other fields that all companies want to use. If you use Jira, you will see the whole IT governance in one system.

With this solution, we can see the full picture in detail, but it can be improved. Resource planning is not easy for our project base.

I would rate Jira a seven out of 10. It will be an eight in the future. I need more time to work on Jira.

We are basically using it to support the UAT tasks. We are also using it for IT support task handling and working together as a team in our company. 

At my workplace, we are using its most updated version.

I'm working in the IT department, and the ticketing system is the most important service for us. We are also using some automation add-ons. It a very good product for handling tickets and tasks and managing processes. It is also very useful and easy to use.

It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great.

There are a few small functions that we are missing in it. For example, you cannot rate a ticket. If you would like to use a rating for a ticket, you cannot give stars or something like that.

I have been using this solution for more than five years.

We rarely come across any issues. Sometimes, it slows down a little bit, and then usually, we just have to rebuild the index. That's all. It needs lots of resources and CPU memory. If the resources are okay, we don't feel any problem with it.

It is probably easier to scale on the cloud. The on-premise is not so scalable, but if you can define the resources, it works well.

In terms of the number of users, we have around 750 users.

We do not directly contact Atlassian. We have a support company that helps us with any situation.

It is simple to initiate or install the product. It is easy and simple, but if you make some designs inside and build some projects with some automatization, it can be more complex.

We first tried to build the system inside the Docker environment, but it was not a success. So, we switched to the normal installation mode. Installing the product and making it work took just a few days. It included building servers and a database.

We do it on our own, but we have some strong support. We have outside support in case of any problem with it.

In terms of maintenance, you have to do the updates. You have to upgrade the system and handle the add-ons versions. If you build the inside environment in the Jira, you always have to fast forward to the project.

We have two teams to handle the maintenance. For standard maintenance, where you are upgrading the versions, we have an IT professional team for it. For the inside environment of the Jira projects and automation functions, we have a service management team.

If you are using just Jira, it is cheap, but if you start to use it and you feel you need some more services or more functions, then you have to buy add-ons, which can make it expensive.

I would recommend this solution. I would rate Jira an eight out of 10. It is definitely not perfect, but it is almost perfect.