Jira Reviews

We use Jira for ticketing purposes, project management, and writing stories, epics, and milestones.

The solution's maintainability, user-friendliness, and learning curve are all very good. We can use the solution's queries to filter everything and get the data out for business processes. Jira queries can be used for different types of deployment automation processes.

The solution should be more user-friendly and include integration with different tools.

I rate the solution a seven to eight out of ten for stability.

The solution’s scalability needs improvement. Around 5,000 users are using Jira in our organization.

The solution’s technical support is quite good.

We previously used ServiceNow. We switched to Jira because it is more user-friendly and an easy-to-use tool for project tracking, project management, and integration. Compared to ServiceNow, Jira is easy to maintain.

The initial setup of the solution is quite complex and should be simplified.

We have seen a 90% return on investment with Jira.

We use Jira for sprint planning and agile project management. We used to maintain a two- or three-week sprint. We found and tracked different user stories, epics, and milestones in that sprint. We used to complete the two-week sprint with all the user stories, epics, and milestones in that particular sprint. We also put the blockers we use in the backlogs so that they could be handled in the next sprint.

Jira's bug tracking and issue resolution works quite well. Users should explore more features and understand and learn more about the solution.

Overall, I rate the solution a seven out of ten.

We use the solution primarily for the IT development processes since we also develop some internal software and integrations. We use it for IT support. We also use the project management features. We help create some custom projects within Jira and assign or dedicate some of the projects to top-level projects. Some are epic projects. We have our own custom project structure within Jira.

The product provides high flexibility to create new workflows quickly. There isn't much work. We use it to track developers' and other IT personnel's time. Everybody enters all the tasks so we can create reports quickly. The integrations are fairly straightforward. The reporting and analytics feature considerably impacts our project management and decision-making process. I rate the impact an eight out of ten.

We had quite a lot of issues integrating BMC Remedy and Jira. They're different. A lot of information needs to be exchanged. The changes that need to be promoted from one on-site to another are challenging. It is easier to integrate Jira with other systems than BMC Remedy. The database has grown since we've been using the tool for 12 years. The performance and stability are visibly degrading since the database has been growing every year.

I have been using the solution for 12 years.

I rate the stability a six out of ten. We have a large database.

The demand is growing. Even though we put in additional and better hardware, the scalability is not what we would like it to be. I rate the scalability a four or five out of ten.

The deployment took a couple of months. We needed a team of five to ten people to deploy the product. I rate the ease of setup a nine out of ten.

I rate the pricing a seven out of ten. The tool is expensive.

We looked for an alternative since Jira’s licensing is expensive. We tested five to six other products. However, we chose Jira because it is quite a solid product. We had a lot of data to migrate and didn't want to spend too much time doing that.

We don't use bug tracking in Jira. I haven't contacted support at all. I’m not responsible for maintaining the Jira deployment. My colleagues take care of it. I might recommend the solution depending on the size and purpose someone wants to use it for. If we don't have personnel to administer Jira, we will have to hire a relatively expensive company to do it. Overall, I rate the product a seven out of ten.

ira is a very complete tool in the tech industry, helping in deploying software. Jira is a very strong tool for a corporation with a team to track and monitor all the tasks that have been defined within a project. It helps teams work and collaborate faster to improve performance. 

I think one of the most powerful features in Jira is the customization of fields and workflow. Jira helps in projects consisting of a workflow by providing templates with the return workflow, we can even modify the workflow and the fields. 

I think the GIS can seem too complex for some people because there are a lot of structures in the software itself. Users need to understand how Jira works, how to define Apex, how to use the storage and many other things. Each template provided by Jira has a different functionality, so users need to explore further about the functions of Jira, especially for the setting and configuration factors. There might be users out there who are unaware of the features in Jira. Otherwise, users will be confused about how to use this tool as it's very complex. 

The product is stable, and in terms of performance, it's really fast. The support team from Jira always informs users in advance, for example, if there is any scheduled maintenance or anything related to the performance tab. I believe Jira also creates maintenance schedules by considering the non-productive hours for each country. Hub fixes and new feature addition time are also planned by Jira for users. 

Jira has a great Knowledge Center, for any kind of questions about how to use the product or other FAQs. Users can check the Knowledge Center before raising a ticket to Jira support. But for some cases, if someone creates a ticket, Jira support is very proactive and follows up on every ticket to provide a solution. Thus, support from Jira is great. I would rate customer support a nine out of ten. 

Positive

Previously before using Jira, we were using Google Workspace because it also has collaborative features. But I think it was missing a lot of features compared to Jira. Jira is specifically created for product or software development, so it's suitable for our business product. Jira has also gone through a lot of improvements over the years since we are using it. 

Not much time is needed to install or configure this tool. You just need to register and subscribe before the tool is ready to use.  

I would rate this product an eight out of ten. 

We had a regulatory requirement through our legislature to collect motor or voter information for residents of California. So, if you basically wanted to sign up to vote, you could do so at a department of motor vehicles. The Jira instance was used for what we call the new motor voter, which is the online premise to register to vote when you conducted a DMV transaction, such as vehicle registration, driver's license, renewal, etc.

We had its latest version. It is online. In the cloud, we set up an account for the department, and then add users as needed. It is a government cloud.

It documented our business requirements.

It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing.

If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side.

Another enhancement could be in the area of interfacing with other products or connectivity. It could have better integration with other tools.

I have been using it since 2017. It has been about five years.

Its stability is good. There are no issues with the performance.

Its scalability is fine. At the peak, we had about 15 users, and towards the end, we had five users.

Our usage was not extensive. We used it only for one project, which was the motor voter project. We don't have any plans to increase the usage. We have stopped paying the subscription fee from the last month because we migrated everything over to ALM Octane for our business requirements.

We didn't need to call them at all.

We were using IBM DOORS Next Generation for business requirements. It was on-premises, and we weren't able to make it available through a URL to the external consultant or workforce. That's why we basically went with Jira. IBM DOORS Next Generation wasn't flexible enough to accommodate all of our remote workforce.

It was straightforward and easy. You basically create an account for your department, and then you onboard your users. There is a subscription fee per user for each month through Confluence. 

It took us a week to get it up and running. It involved reading, studying it, figuring it out, and then doing it. It was pretty simple to set up data and add users. So, we onboarded it within a week.

The challenge for us while setting it up was that we had to put it on a credit card, which is not a good thing for the government. Typically, the government likes to pay through a purchase order or procurement process, but because it was a monthly subscription fee, it had to be on a credit card. We had to use an executive card in order for us to pay the bill every month, which was really kind of a pain because our accounting office always had to make sure and check the number of users. They would ask if I had 15 users this month. I am the administrator of the application, so, of course, I know how many users are there. I can see how many users are there and how many are using it and remove them if they don't. I think the state just needs to modify its procurement process because I think ours is pretty old school. I don't think that Atlassian needs to adapt to ours, but that was the only challenge we had in setting it up and configuring.

We had an in-house as well as a procured consultant, but he was through the state, not directly with Jira or Confluence.

The ballpark figure is about $100 a month.

It is easy to use and easy to onboard. It has got a good foundation of offerings for the business requirements if you're working on an agile project or user stories.

I would rate Jira a seven out of 10.

I use Jira in my company for my projects or the tasks assigned via the tool. I also use Jira as a scrum tool.

The solution's most valuable feature is that I used the tool to deal with bugs. In my project, with the bug assigned to me by my company, I was given the backlog and the code. Whenever I had to add it, I used to request Git for code push, pull, and merge, and then I used to paste that GitID into Jira. It was very easy for the other developers to handle whatever code I did.

At times, I am not able to report a bug. Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required.

I have been using Jira for two years. My company is a customer of the tool.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

With the latest versions being released, I feel Jira is being improved daily.

My previous organization used Jira, and now, my current company also uses it.

The solution's technical support needs just to understand the customers' environments and improve or provide a better version of the tool. I rate the technical support a nine out of ten.

Positive

The product's initial setup phase is easy.

The solution is deployed on the cloud.

It is an affordable tool.

From a project management perspective, my project manager assigned some Jira tickets, and I started to do it on a weekly and daily basis. I send a request to a Jira ticket to open it, and during the process, I start describing how I am replicating that issue, explaining it in that Jira ticket. After that, I resolved that Jira ticket put that Git code in the expression part, and submitted it.

Regarding reporting and analytics features, my company uses Jira for software development projects as if it were a single tool. My company uses the tool in a manner where we send requests to one developer, and they open a Jira ticket using the email. Every day, they update so that everybody is able to see it without any description, while my team can see what the developer is doing daily. If a developer is updating, everybody can see that in the company. The tool is very easy to use, and it is easy to understand areas like script planning, story points, and backlog grooming.

I recommend the product to those who plan to use it. I worked with two scrum tools. In Azure also, my company uses scrum, which is a little bit uncomfortable for me, but I am very comfortable with Jira, a major reason I suggest it to other people.

I rate the overall tool a nine out of ten.

I use it for hours tracking with Tempo login, task management, project management, and time booking with the Tempo plugin.

Jira supports our bug-tracking process. We use reports to track bugs. We create reports, and then the issues are fixed.

We have also customized Jira with add-ons and integrations. For example, we use the Tempo plugin for time booking.

I like that there are a lot of features and options, like the Kanban board and other ways to customize projects, columns, and fields.

Jira's reporting and analytics features are also good. 

For project management analytics, we use features like cost tracking, etc.

Integration is good. A lot of tools we use can connect to Jira using the API, making things easier.

ClickUp is a good alternative to Jira, so they have a better interface [GUI]. I don't like Jira's graphical interface - it could be more user-friendly. Jira looks old school. 

Also, the administration part of Jira should be simpler for project managers and Jira administrators. It has many configuration areas, which can be confusing.

So, the administration part could be more simplified. 

I have been using it for ten years. 

It is quite stable. I would rate the stability a ten out of ten. 

ClickUp has more features, so I'd rate Jira around seven for scalability.

On average there are around 500 end users using this solution. 

For some projects I'm involved in, we use the cloud version. Most of our clients are moving to the cloud.

On-premise, because it has more features than the cloud version, or at least the cloud versions our clients have purchased.

Overall, I would rate the solution a nine out of ten. I would recommend using this solution. Go for it! 

I use it to manage my scrum projects and some of the Kanban projects.

In terms of version, they have been updating it every three weeks. It is a kind of a sprint that they do, just like Google Chrome. So, there is no going back and forth. We use a cloud-based application. So, it is always the updated one.

The type of cloud depends on the client. I've been through all kinds of situations: completely public, semi-public, and private. If it is a public cloud, then it is directly from Atlassian. They are providing it. So, there is no middleware.

It definitely streamlined the process of managing the projects. Earlier, we had a system scattered all over the place. We had information in Excel, Microsoft Project, and some of the other applications that we have, but now, we have everything in Jira itself. So, we create user stories and groom the product backlog. We have kept everything in Jira. It is our single source for project information that anyone can go to. So, we could see a lot of transparency with Jira.

Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports.

It is good for single projects, but if you have to manage the portfolio level of the projects, they have a few add-ons that we need to buy and integrate. They can improve this part to manage it in a better way.

It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free.

There could also be some additional reports.

I have been using Jira for seven to eight years.

Stability-wise, it is very good. It is very lightweight. I have used other enterprise-level products to manage the same kind of scrum and Kanban projects and other projects. Other products have many enterprise-level features, but they're very slow and kind of hard to manage.

It is a cloud-based one, so I don't see much difficulty in scaling it. If you want to go from 100 users to 200 users, you will be able to do it without much hassle.

I've been doing a lot of consulting. So, I've seen from five users to the entire organization with more than 500 people using it.

I did contact them through email and discussion forums. I had a limited opportunity to work with them. So, I don't know much about their support.

Jira is a kind of the last one I settled on. Before that, I have used products such as Rally and VersionOne. These two are enterprise-level scrum and Kanban tools that are similar to Jira. 

I have also used Asana and Trello. Trello is lightweight, but I wouldn't call it equivalent to Jira. Jira has many features that not many solutions have. 

Most of the time, we are working with the cloud-based one. So, we don't have to set up everything. It is all there. You just buy a monthly subscription package. The workflow configuration, however, would be a bit difficult while you're trying to set it up. In addition, if you have to go down to the permission level, it is a bit different.

Workflow-wise, you need to plan well because once you configure it, you cannot often change a workflow. For each project, the workflow might be different. You might have a development team, a QA team, a configuration team, and a deployment team. When you start a task, you just need to make sure you are covering everyone. In terms of the workflow, you should know what would happen if someone is not there, and what are you going to do. So, you need to make sure that you are covering those things. Other than that, you need to know how much you are going to take care of the hierarchical level permissions. These are two primary things, and then, later on, you can relabel quite a lot of things in terms of how you're using the backlog product and user stories.

I would rate Jira an eight out of 10.

Jira is used for all the project management, on all the stages of project management. So then we create a Kanban board and move on to creating the stories.

We create the story points, break down the requirements, and then create the Sprint accordingly. Based on that, we can manage in Jira how many user stories we will pick in what Sprint. And based on the dependencies of the user stories, this is the flexibility that Jira provides. Then we have also got various, you know, sub-tasks, which we have to complete to accomplish the DoD (Definition of Done). We can mark the Sprint as complete when these particular tasks are completed. So that gives very good monitoring of the project where the project is

going on.

When it comes to the testing part, so testing is end-to-end on Jira. We can take the user stories based on the acceptance criteria. The test cases are created in Jira, and the business analyst team reviews those test cases. Based on their feedback, the test cases are updated. Those test cases are being executed. So there is clear tracking of the test execution, and all the test cases are also linked with the user storage. We have end-to-end tracking of what test case is executed for what user story. So that is the best part of Jira.

The monitoring, flexibility and tracking are really good in Jira.

When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect.

I have been using Jira for eight years. 

Jira is a stable product. I have seen the growth in the solution’s stability for the last eight years. The current version is quite stable and is a robust system.

Overall, the solution is scalable. Jira is quite easy to scale. If we have five projects working on Jira and we have about five more projects to be incorporated, it's easy to install Jira for those five projects as well. Presently, twenty five thousand users are using Jira. 

We have been using this for the last eight years and we are quite accustomed to that. We don’t need much support from Jira or Atlassian. Yes, but we have got an enterprise version of that, and their support is quite quick.

Positive

I was using HPE Quality Management Tool.

The initial setup of Jira is very easy. I have been an administrator, so I would say that because used to it. But in comparison to other systems, yeah, it’s quite easy and user-friendly. The deployment takes two to three days of time. Forty people are required for the maintenance of the solution.

I implemented it myself as an administrator of Jira.

Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost.

Use all the reports which are generated. You have to make a system for the process. Here is a small example during a subtask. The time input via the source is not mandatory. But you have to make it mandatory either from the back end.

You’ll not be able to fetch the reports on the performance, the health of the project, capacity management, or IT management if the data is not input properly. So this is something which people most people don’t take care of as a Jira planning. But when you plan a project, you have to plan these things.

I rate the overall solution a seven out of ten.