Jira Reviews

It's scalable.

It's easy to deploy.

The cost of the solution seems to be reasonable. 

Once the solution is deployed, it's not easy to configure. If you have a lot of capability, it's very dynamic from the back end. Therefore, when setting up the workflows, it can be a little bit complex. We did a lot of functions on managing the development and that's why maybe it's a little bit complex. Basically, in order to design a workflow in Jira, it's not a straightforward task.

From a feature perspective, not much is missing. However, they need to put some investment into the user experience. It needs to be easier to use, more friendly, especially on the configuration part. It's a hassle. You need to deal with a high learning curve in order to understand how it's configured and how it can work.

We've used the solution for more than eight years now.

The solution is scalable. 

We have more than 50 people using Jira at this time. 

We do plan to increase usage. We are growing. Since we are growing, we are increasing Jira as each member on the technology team needs an account for development, business analysis, or testing.

While the initial setup is pretty simple and straightforward, handling the configurations and the workflows can be complex. 

I didn't attend this in the development phase. In testing, I did the same effort and it took me a month to set up while I was deploying a test stream. I worked on the testing workflow as well, the defect workflow. That said, I don't know how long it takes for them to configure Jira.

We handled the setup in-house.

The licensing is per unit. My understanding is that it is pretty affordable. However, I don't directly deal with licensing.

We are just a customer and an end-user.

From a testing point of view, I would rate it at a six out of ten. I use it as a defect management tool, and it, for me, it's not easy to use.

Some of the use cases are for tracking issues and bugs.

I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan.

The solution is deployed on-premises.

The solution is valuable because it's pretty flexible. It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company.

The solution could be more user-friendly.

I have been working with Jira within the past year.

The solution is pretty stable.

The solution is scalable. There are a few dozen users using this solution. We might increase the usage in the future.

I previously worked with ClickUp and would suggest using it. It's a competitor to Atlassian Jira.

When it comes to functionality and usability, I think ClickUp is better, but compared to Jira, ClickUp's drawback is their integrations with other products. The product is not old enough to be mature.

Jira is more flexible and more integrative with other products, and ClickUp is more user-friendly. The functionality is pretty rich.

I would rate this solution 9 out of 10. 

The only thing that I'd like to advise is to just monitor the market and keep an eye on comparison between the Jira and ClickUp.

It is helpful for bug tracking in software development. If developers are doing some work and testers notice some defects, they can flag it in JIRA. For example, I track my day-to-day work in JIRA so that others know what I'm working on. They can look at JIRA and don't need to contact me. From JIRA, they can find out that I am working on this project and spent two days on it, etc. It's used for so many things, like task management, bug tracking, and release management. 

JIRA is not for deployment. For deployment, you are going to use some tools like Jenkins. It's meant for all the features that are going into that deployment. 

Different teams within the company use JIRA. For example, everybody in the engineering section uses it, so altogether, that's around 200 people.

JIRA gives us a lot of visibility. For example, if you're planning to release a given feature, you can track the status of that feature. Is it working correctly, or does it have some bugs? So you have a high level of visibility on the work. 

The JIRA user interface looks great. It's an overall good experience. It's very intuitive in the sense that you understand how it's going to work. It's very self-explanatory, and it's beneficial overall. Each release has different steps and phases, and the whole thing can mostly be captured on JIRA. The workflows are really helpful. 

So at one point in time, they did a huge UI upgrade. At that time, I felt like they had changed something, so it was hard to figure out. Now that we are habituated, it's not an issue now. We had gotten used to the old interface, so things changed, we felt an initial discomfort. That's the only thing. Otherwise, there is nothing I dislike about JIRA.

I've used JIRA since the beginning of my career and nothing else.

I haven't had any issues with JIRA's stability so far.

The scalability of JIRA has always been good. The response time is always fast. I've never had any issues with scalability. I think no matter how much our usage increases, we'll continue to use JIRA.  But, I think our usage is at an optimal level. 

From our end, setup is basically book-keeping. I can't say much about the overall setup because there is an administrator for JIRA who adds users and sets everything up. I haven't been an administrator. I'm just consuming the JIRA. 

Initially, I think administrators are going to set some things like configuring the workflow should and then how you want to say things. But other than that, if you set it up once, it's going to work. You don't have to do much maintenance.

I rate JIRA nine out of 10. I would recommend it.

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. 

We use Jira every day for tasks like tracking product deployments, mapping it to the tools that we use, and sprint tracking. We also used it for audit purposes, where everybody goes back to that for details about each user story.

Each sprint tracking is done in there, as well as the other product-related activities

All aspects of Jira administration help with respect to QA development and deployment.

This solution allows us to use customized workloads for different projects.

The sprint tracking is really helpful and very convenient.

Scrum boards are very easy to follow and we use them every day.

The roadmap, to understand what our team is going, is quite helpful when it comes to understanding things in a visual format. It provides good visuals such as the Burnup Chart.

Requirement traceability is easier to do with this product.

It integrates well with other tools.

We have been working on integrating Jira with Confluence for the past months but it is not yet working. Having more seamless integration with Confluence would really help us track our product management activity and other product details in one place.

Integration with BitBucket would allow us to have a better deployment process.

I have been using Jira for between four and five years.

This product is very much stable, and we have every tracking option being used.

It scales well, from what we have seen. We have more than 350 users that are in groups, and perhaps another 150 in addition to that. We are onboarding a lot of teams.

When I need support, I contact our in-house technical team. I have not spoken with anybody from outside the organization or anybody from Atlassian.

We were using the on-premises version until a year or two ago when we migrated to the cloud version.

The initial setup was simple and it didn't take much time to complete.

We have an in-house team to deploy and manage our IT solutions. There may have been some outside help initially but everything is now done in-house.

We have an enterprise license that includes cloud service and support.

Overall, this is a very good product and I think that it is the best project management tool. It is used company-wide and I recommend it.

I would rate this solution a nine out of ten.

Our primary use case for Jira is for requests for tracking the software development.

We use Jira for the process, especially for password tracking. We're the issue management team for development. We are quite new, so I was very interested in ITSM documentation provided by Jira. But, I needed time to readjust that to our organization as per the line of business.

Overall I think it's helpful, but I need some time to absorb all the knowledge.

People have different opinions about whether it has improved our organization. I think it is quite a valuable tool and platform to streamline tasks, make project plans, and manage the release events.

The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence. The documentation is another supporting part for development. I didn't go that deep, so that's what I see as the end user.

In general, it's very convenient for people that work in the software development business.

In terms of what could be improved, it is a bit harder for management or the business partners. I used to search the Atlassian Community online for some troubleshooting issues and I think there were some issues that seemed to not be a big problem for other similar applications, like Microsoft Teams, that were not considered by Jira.

So I hope those will be considered soon. I think for some, the help documentation has been hard to track, so that I had a bit of difficulty finding the solutions. I'm the end user. I'm not the problem solver.

I have been using Jira for less than a year.

It does have some bugs or glitches sometimes. Like with Confluence, it always has some glitches, like the last edits I made minutes ago. It happens sometimes.

I don't know about the scalability. I just use the very basic one. 

Only our IT people are using it. It's easier for IT people to understand it than anyone else.

We have our technical support from our vendor. They are very supportive.

No, we didn't use another solution previously. We used to manage those processes manually, like the spreadsheet. That's why we would like to switch to the Atlassian platform for some automations and for a mature platform to help us.

We had our vendor help to set up originally. Later, we made some customizations by other means. But because this is still at a very early age for us, it's a bit random on previous customizations. There were some blockages for people to understand from different perspectives. But I think so far the business people may not understand those procedures because it was originally designed for the coders and for the software development business.

We are using the Community license for Jira since we are a not-for-profit organization.

I think the technical support and the customization of the line of business are the most important points for me as a BA. I don't think the license for a business is low. 

We think - so far so good. 

On a scale of one to ten, I would give Jira an eight out of 10.

Nothing is perfect.

We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there. With that, I am able to create a kind of gauge, estimate, and forecast our capacity planning for the next two weeks. We use it to create peer reports.

A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time. So I have to do multiple exports to just create the sub-tasks and sub-tasks are not being reported. If I wanted to export this and recreate this in another platform like Azure DevOps, I would have a problem right now.

I have been using Jira for four months. 

The support person I contacted was not skilled enough to provide me the answer so it's up in the air.I'm just doing multiple exports. 

Jira as it is, is a very nice tool. For capacity planning and resourcing, I think it is not built for this and we are trying to make use of it in that area.

I would rate Jira a seven out of ten.

We use this solution for Agile project management and BAU work delivery in sprints / DevOps.

This solution has helped with team collaboration and task delivery.

The most valuable feature is the Burndown Chart to see work that is outstanding.

The reporting needs to be improved.