Jira Reviews

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.

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.

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 use Jira for task tracking, sprint planning, and backlog.

The dashboards are useful. You have visibility across projects and various dashboards.

The status of the different activities is also helpful 

In general, it is not user-friendly. 

For a non-technical person to use, Jira is not intuitive. If you are a developer it's fine, but we are trying to get other technical people in to look at tasks or to update a task, move it from one sprint to another sprint and it takes more effort than I would like.

I would just like to see it easier to use, and I would like the workflows to be less complex to do what we need them to do.

My experience with Jira is limited, but the organization has been using Jira for three years.

We are using the latest version.

Jira is stable. to my knowledge, we have not had any issues with bugs or glitches.

The scalability can be complex if you are using workflows.

We have approximately 20 developers and some managers in our organization who use Jira. 

I have not yet used Jira technical support.

Previously, we did not use another solution. We started with Jira.

Along with Jira, we use Microsoft Azure DevOps.

The initial setup is fairly straightforward. 

It was fairly simple for us.

I would recommend getting sound knowledge first. It is difficult to go back later to fix things, so try to build it right the first time.

For the functionality that exists, I think that it's good.

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

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.

We use Jira to manage all our software development projects and our engineering projects. Our main use of the solution is for the workflows on our different types of projects. It's mainly used by our engineering groups, they have the proper workflows and all of the stats. As a director, I work more at the business level, tracking tasks similar to the new planner that's in Microsoft which some people are switching to. We also use it in the backend of the projects. For project managers and directors, it's more about a to-do list thing that's shared. I'm a company director and we are customers of Jira. 

The online collaborative nature of the solution has been helpful. Previously, coordination was done in Microsoft Project and Excel spreadsheets. The level of collaboration and the accessibility of the information which Jira offers has greatly improved things and we've also been able to build out and fine tune the workflows and the integration into the different tool sets. We're definitely going to keep using Jira.

I think the customization and tailoring of the workflows have proven to be very useful. And then there's the collaboration of the tool itself which has a lot of nice features. 

One of the issues is tracking the hours that people spend on each task. I know the solution has some built-in features but it doesn't quite meet our needs. We tried a couple of expansions unsuccessfully. Being able to track the effort on each of the tasks is important for us and we'd also like to be able to compare that with what's been budgeted. It would be useful. We've recently moved to Teams and some of the integration with Teams doesn't seem to work, whether it's not supported or not there, the ability to integrate that would be something we'd like to see. 

We've been using this solution for over five years. 

We haven't had any issues with stability. 

We're a fairly small organization. We've scaled up to around 500 users and we haven't had any issues with that. It's mainly used by our engineering group, and our active users use it all the time, on a daily basis. We'll increase as we organically grow. 

I can't recall the initial setup but it took us a while to figure out exactly how to use it. We deployed using our own staff. 

I don't know what the licensing costs are but we find them affordable. It's never been a major issue.

This is a powerful tool and allows a lot of collaboration, it's worth spending some time figuring out how your workflows will be, that's where the real value is.

I rate this solution an eight out of 10. 

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.