Jira Reviews

We use Jira for our in-house projects. We use Jira Cloud and Bitbucket. We are not actively using Confluence.

We are a small company. We can manage our project tasks with other tools, but I prefer to use Jira on the cloud because people forget what they have done, and we need to see who did which task and when.

We love the bulk edit feature. Jira also integrates well with Bitbucket. 

Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows.

I have been using this solution for three years.

It is very stable. I have been using this solution for three years, and I never had to contact their support.

It is scalable. We have six people who use Jira at the moment, and they don't have any issues related to slow response. Everything is fine for now.

I never had to contact their support.

In this company, I have only used Jira. In earlier companies, I have used other tools such as Microsoft Project, Redmine, and Service Bus. 

It is easy to set up. We can use project templates. We can use classic projects templates or create new templates. Classic is enough for us. Our management doesn't want reports from us. We use templates for our daily progress.

Its price is good and similar to other products. It is about five or six dollars per user.

I got it set up when I joined this company, and now I manage users here. It has integration with Bitbucket. It is fine for us.

I would rate Jira a nine out of 10.

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 use it for IT project management. We manage the timelines and resources, mainly people resources.

It is a stable solution, and we have had no issues with stability.

For our company, we're thinking about not only project management solutions but also collaboration solutions, and maybe if Jira had a chart or quick commenting option, it would be great.

I've been working with it for two years. It is a cloud-based solution.

We have had no issues with stability.

We currently have ten users, and it is free for ten users. However, we hope to increase usage.

I would rate Jira at eight on a scale from one to ten.

I'm a consulting company. I provide solutions for many companies, and in some cases, I implement Jira. DevOps is something else that I provide for my clients.

Our clients range in all sizes. I have microscopic clients, such as a one-man company, and on the other end of the spectrum, I have the New Zealand government, for example.

The most valuable feature of Jira is that it's a well-known tool that many people are familiar with.

Jira is not the best tool; I just don't like it.

I am not looking to improve Jira. I have transitioned to using Azure DevOps or GitHub.

I don't like the interface or the way it is structured. I prefer the way it is done in Azure DevOps.

It is not user-friendly.

I have been acquainted with Jira for approximately five years.

Jira is a stable solution.

I have not contacted technical support.

We are also providing Azure DevOps.

I would recommend DevOps because it is more user-friendly and easier to use.

I was not involved in the initial setup of Jira.

I would rate Jira a five out of ten.

We use it mainly for logging defects and tracking them.

The UI is good. It's simple and not very complicated.

It's very good for tracking.

The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details.

I don't think Jira has a copy/paste option for emails. I know that you can attach emails, but I don't think there is a copy/paste option.

I've been working with JIRA for the past 10 years.

I would recommend Jira because it helps from a functional point of view and also with tracking defects. It is similar to Quality Center and is good.

I would rate it at seven on a scale from one to ten.

We mainly use the solution for project management. We are using Jira for our software development purposes only. Usually, we create a Jira project for each project and develop it according to its size. We assign team members who will belong to those projects, each project. Then, we manage everything using Jira.

Basically, the main purpose of using Jira is just planning and then checking issues. That's all for now.

We can lean on Jira completely during projects, even in terms of all the small things, surrounding planning. There are error reports, and we can take in the progress. We are not using any other tool except Jira for managing software development, including the testing and reports and following up.

Overall, the solution is very nice and has a variety of great features. 

The stability of the solution has been quite good.

We haven't had any issues with scalability.

It's a very useful project management tool.

For me, the solution is too complicated as it has too many features. It would be nice if they could streamline things.

They can make it a little bit better in terms of the user interface. Some things are very scattered. It is a bit confusing. They developed a new user interface, and I cannot follow the changes. There's documentation, however, it's not so good.

The solution has a pretty steep learning curve. It would be great if they could lessen the learning curve by providing more templates and ready-made options for new users to take advantage of.

I've been using the solution for almost two years. It's been a while.

In terms of stability, we haven't experienced any crash or anything like that. There are no bugs or glitches. We haven't suffered any issue with the Jira service itself so far.

Due to the fact that we are using the cloud service of Jira, we don't have any experience with any lagging or delaying or any of those kinds of issues yet. The team is managing this scalability and can scale up and down their resources automatically in the background. I don't have any issues with the scalability that's provided.

We are a small organization. We only have a team of 20 developers. We might increase usage in the future, should our team grow.

We haven't had to reach out to technical support just yet. I can't speak to how helpful or responsive they are.

I wasn't directly involved in the implementation process. I can't speak to what cloud the product is on or the exact details of the deployment.

We have only two people for the Jira management. We are only paying attention to security. We ensure we are giving the right permission to the right person, that is the only factor we are focusing on. 

We are just customers and end-users.

As we are using the cloud version of the solution, we are always on the most up-to-date version.

For simple project management, Jira is too much. If you want to manage a project precisely, however, then I can recommend Jira. It's not only a software-specific version. There are different versions of Jira so that you can apply it to different areas - not just software. That is one good aspect. I'd say that it is very polished, and has a very well-defined approach to project management. 

I'd rate the solution at a nine out of ten. We've mostly been happy with how it's worked for us.

Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so.

We regularly check the tasks assigned to us, day by day, and create a work log in that task according to what has been done.

You can check today's task assigned to you by using a custom filter, which you can create on your own. We can also make a customized dashboard user-wise.

Upper-level management can analyze the chart and get an overview of the project, giving them the ability to estimate the budget and release date of the project.

After purchasing Jira, we started shifting to it from the older software we used, like Bugzilla. Bugzilla was being used as our bug reporting tool but after the introduction of Jira, we began to use several of its features. We now use Jira for Scrum Planning, Bug Reporting, Time Tracking, and Budget Tracking.

Day by day, the transparency of the project improves and estimating the project release date becomes easier to do. It is also easy for management-level users to check the project's budget and estimate the release date for a specific feature.

Because there are a number of charts available, looking at them will assist you with any decision that is related to your project.

As a user of the Jira, rather than an administrator, the custom dashboard and custom filter are some of the best features from my perspective.

I can manage my own dashboard and by logging into my account every day, I can get information about the day's tasks assigned to me. I can also see my timeline chart, and using that, I can see and understand what has been done in the last week/month.

I have added a gadget on my dashboard that gives me regular updates on the bugs reported by the QA team.

Jira is one of the best software applications for project management and budget tracking, but it does have some issues, as follows:

• Firstly, the filtering feature can be improved to some degree.
• Because JIRA has so many features, it may take some time to obtain a general knowledge of each one.
• In order to enhance adoption in small and medium businesses, the cost should be improved.
• I believe it will be difficult for new users to understand.
• There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported.

In our organization, we have been Jira since 2017.

Previously, we were using the Bugzilla bug tracking software for reporting bugs from the QA and FITs. Due to the number of problems that we had with it, we purchased Jira and have been using it for approximately five years.

The initial setup was easy, and we haven't found any difficulty in that.

The pricing is much higher than other similar solutions available in the market, and as such, the vendor should think about a price reduction to make this product more affordable.

We did not evaluate other options before implementing Jira.