Jira Reviews

We use Jira primarily for project management within the organization. It helps us manage tasks, bug management, and tracking tickets effectively. We assign tickets to individual team members and track them easily.

For project management, Jira has helped facilitate efficient task segregation and allocation to employees. It allows us to track projects comprehensively and improves the overall management from a project perspective.

Jira is a comprehensive tool for managing projects. It helps in task segregation and assignment, making it time-efficient for employees. From a project management perspective, it allows easy tracking and management of tasks. Furthermore, Jira is user-friendly with a seamless deployment process.

We haven't seen Jira's progressive area so far, and we are not sure what it might do in the future. Due to Jira's access controls and role-based functionalities, we have some limitations, limiting our full exploration of its capabilities.

We have not encountered any issues with Jira so far. It has proven to be a stable tool for our needs.

Jira is available at the enterprise level, and while it is a user-based aggregation, we are unable to access all its features due to role-based access controls.

We operate under a nonlimited license with Jira, allowing a number of users to access it with a single enterprise license.

ESQ and Prognosis, which is sold by IR Transact, were discussed as tools used for monitoring. However, these are unrelated to our use of Jira.

If anyone needs a project management tool, I would definitely recommend Jira based on my experience. However, the specific functionalities you can use might depend on the role-based access and permissions within the organization.

I use Jira for sprint planning and tracking projects. I can create boards on it. And then I just have backlogs, and I just basically plan and sprint for the next two weeks, and you just put anything on the to-do list, doing, and done through the board. So it's very simple. It’s all drag and drop. There’s nothing too complex around it. 

The main thing is making sure whatever you're planning for your sprint is covered there, and then you can run reports after that.  Sometimes, the key issue I've seen with project failures is when the sprint planning isn't comprehensive enough.  It’s not being covered. But generally, it's very similar to Microsoft Project, in some ways because you can still create those Kanban boards and run things, but nothing too crazy.

Our client engagements are usually for a specific period. From an analytics perspective, long-term tracking is probably better handled on the client's end, not ours, as we're not there long enough to gather meaningful data.

I am aware of the bug-tracking function in Jira. We mention the bug on the ticket itself, whatever ticket we're working on, but we don't track the bug separately. Only because once the ticket closes, the bug sort of closes with it. For ongoing bugs, that's a different place to store the information, not on Jira. That's just my opinion. 

Anything that's open should be stored in Jira; otherwise, it will get lost. So, I don't feel that's the right place to keep ongoing bugs.

It is easy to integrate Jira within our current IT environment. Jira has connectors and supports various integrations, but again, we don't overcomplicate our setup. We keep our Jira usage simple. I've generally seen it integrate well, so I don't think it should be an issue.

We just use it for very basic purposes. 

I like its ease of use. It doesn't require too much training. Even if I gave it to someone who hasn't gotten Jira experience, I feel like it's simple enough for them to figure it out. 

It's not that complex, which is quite nice. And the fact that you can run reports quite easily. You know, the actual visual side is quite nice. You can tag people to it. I think all of that makes it a simple tool that's easy to interact and collaborate with.

Sometimes the screens can be a bit too busy. There's often a lot of information on the screen. I think paring things down and applying some UX improvements might enhance the look and feel of the interface. But generally, it's fine for my use cases.  

Perhaps some AI integration, like a co-pilot feature, could be a massive improvement. This is similar to how Microsoft introduced AI tools. That would be helpful, as I don't believe Jira has a great product in that space at the moment.

I have been using it for a few years now. It has been maybe seven years. 

It's been very stable. I haven't seen any bugs or experienced any downtime.

Overall, I would rate the stability a ten out of ten. 

From my experience, it scales quite well. I would rate the scalability an eight out of ten. 

So, it's easy to scale with no issues or complexities. From a functionality perspective, anyone can use it. Obviously, the cost would change depending on the size of the company. If it's too expensive, then it might not be suitable for a smaller company.  

I've never had to raise anything. Jira is fairly straightforward, and we're not using it for overly complex tasks. So, personally, I've never needed Atlassian's tech support.

I have also used Microsoft Project. 

Microsoft Project feels more like Excel, while Jira is quite distinct. Jira is probably slightly better because it doesn't require any downloads. But, for me – both are good options.

The initial setup for Jira is pretty simple. I don't think it's hard.

Overall, I would rate the solution an eight out of ten. In most cases, when I'm working with clients that don't already have a project management tool, I usually suggest trying Jira.

We manage our sprints and backlog using Jira.

It is implemented for everything. The project works whether it's in development or production. Everything has to go through Jira. Jira is integral to it all.

So, Jira has been instrumental in book tracking for our team.

For software development, we use the Kanban board or the Sprint board to manage backlogs, sprint management, and sprint reports. All communication happens through Jira. This includes requirement details, questions, estimates, and actual hours worked. We use Jira extensively.

I like the Sprint board. 

In Jira, the integrations I have used so far are the repository integration, like when it gets added, or the integration with Confluence, which is good. Both work great, Confluence as well as Bitbucket integration.

Jira’s customization ability and workflows in boards is beneficial. We have already seen some workflow setups, so the flexibility and that feature is there. And we do ask for some custom page flow if needed. So, that's good.

There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there. We can know the capacity and what happened with the whole sprint, but not for an individual person to see where it's falling and how it's tracking.

Report and analytics capabilities are important for a product manager. That visibility is important, so we use Jira. Some of the features are there, and I use my own Excels or other data things to compensate for that.

I have been using it for a couple of years. It has been ten years.  

I would rate the stability a nine out of ten. 

Scalability seems good because the whole enterprise is using it, and we don't see any issues.

Everybody uses it like 10,000+, at least.

I can Google how things need to be done. I see the options in the community support for resolutions. 

Setup is pretty straightforward. All good. I've never had a challenge.

I would rate my experience with the initial setup a nine out of ten, with one being difficult and ten being easy. 

It was already in a place when I joined the company.

I will recommend using Jira because it is easy to use, it's straightforward, and more browser-based, so that makes it easier.

Overall, I would rate Jira a nine out of ten.

I use Jira in many cases when developing software. For example, I often use it for gathering software requirements, checking management, and issue tracking. Sometimes, I use it for planning my software development. I create some pictures and activities for my software planning, so I usually use Jira for my entire software development life cycle.

Jira is very useful for us, so we can set the resource and time because Jira gives us some dashboard. We can track and manage the due date of issues using Jira. It allows us to check the project status by using the Jira Dashboard.

There are many features in Jira. Our team uses Kanban and Sprint from Jira. It is very convenient to connect Jira with Teams and Slack. Jira's integration with our workflow is deep, and we rely on it heavily for software development. Jira's ability to streamline processes is crucial. It's a user-friendly tool that supports many kinds of APIs, and we can easily create dashboards.

Nowadays, AI is a very dominant function. I would like Jira to adapt AI functionality, which would be useful for finding issues or the status of the development plan. If AI functionality were integrated, it would provide useful features like searching for types of issues within Jira.

I have been working with Jira for eleven years.

Sometimes, there is a problem when Jira needs to sync data. During these times, we have to wait and can't use Jira. Although this kind of work is usually done over the weekend, it can cause trouble if we need to work during that time. After syncing, some errors occur but very rarely.

As a user, I find Jira to be a very scalable tool. We have no problems when using Jira, indicating it is quite scalable.

I usually ask for help from my colleagues. I do not contact Atlassian or their support directly.

Positive

I used Polarium before Jira, but I did not like it. I find Jira to be more user-friendly, with many types of APIs.

Our team makes tools using Jira API. It supports many APIs, so we can create our functions and tools. Overall, I'd rate the initial setup experience as an eight or nine from one to ten.

I have evaluated Polarium before.

I recommend Jira for project management. It is very convenient to manage issues or product plans and supports many kinds of APIs. It's easy to create dashboards. Overall, I would rate Jira nine out of ten.

My primary use case involves creating tickets and tracking them in Jira. I am responsible for planning iterations and PIs, and I make use of the AI features for summarizing tickets.

Jira is user-friendly and offers many features. The AI integration, particularly for summarizing tickets, is extremely valuable as it simplifies understanding ticket content without delving into detailed descriptions. The user interface is nice to use, and the workflow automation could potentially make operations simpler.

To improve Jira, providing proper documentation, examples, or snippets for scripting workflows would be beneficial. It would simplify the user experience, making the automation process easier.

I have been an end user of Jira for almost four years.

I do not see any issues with the stability of Jira.

I am not aware of the scalability specifics since I am just an end user.

Previously, we used Jama. It has been out of scope for a few years and Jira took its place. This was a company decision, and globally, our company is now using Microsoft Azure.

I am satisfied with Jira and would rate the overall solution a ten out of ten.

We follow an Agile framework and use Jira for sprint planning and management.

The scrum dashboard is the product's most important feature. It provides an overview of tasks, who is working on what, and the status of each task.

It offers very good APIs for creating custom integrations and has many built-in integrations with other tools.

The solution heavily focuses on the Agile framework, which might only suit some business use cases. This particular area needs enhancement. 

I've been using Jira for about three years.

The platform is very stable. I haven't faced any stability issues with it.

Approximately 70 to 80 people are using Jira in our organization. It is a scalable product. 

Setting up Jira takes some time. You need to create dashboards, configure settings, and test those configurations. The default setup is straightforward, but understanding and applying the various configurations can be time-consuming.

For smaller organizations, it might be better to consider alternatives like Linear.io. But if you need an integrated system, especially with other Atlassian products, Jira is a solid choice.

It is widely used, so the transition is easier if someone moves from one organization to another that also uses it. Additionally, its automation features are powerful and can address many use cases.

The reports are useful, giving an overview of a sprint's progress and indicating areas for improvement. However, I have yet to use the analytics feature much.

I rate it a seven out of ten. 

We use the solution for secure software development. Additionally, we use the service-based system.

If our software factory delivers, individuals will need to provide instructions on how to use the software factory.

The integration is nice. We can integrate with TeamViewer and many more solutions. We need to go into Jira to complete the secure software delivery.

The solution could be cheaper.

I have been using Jira for ten years. We are using the cloud version of the solution.

The product is very stable.

I rate the solution’s stability a ten out of ten.

The solution’s scalability is good.

100 users are using this solution.

I rate the solution’s scalability a seven out of ten.

Jira is providing all information.

Positive

Migrating from an old server agent is quite complicated.

We have a very small organisation. Two IT people are needed for the solution’s deployment.

I rate the initial setup a six out of ten, where one is difficult, and ten is easy.

The product is quite expensive. It costs approximately 1.2 million rand per year.

It's a fixed price, depending on the modules that you get. You have specific tools, that's what you pay for.

I rate the product’s pricing a seven out of ten, where one is cheap and ten is expensive.

I would advise people to use Jira. There are other open-source products available that individuals can consider first, depending on the company's budget. Jira is a fairly stable product, but there are other open-source solutions worth exploring.

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

My company doesn't use Jira for service desk management. My organization uses Jira in areas like user stories, ticket tracking for work, dashboards, and kanban boards.

The product has improved my organization since it provides a common point of reference for tracking work from different groups, including developers, QAs, and project management areas.

The most valuable feature of the solution is the ease of replication of tickets.

The documentation on how to create dashboards and take advantage of other features in the tool are areas where the tool has certain shortcomings. The tool needs to have documentation on how to take advantage of different features in general.

In the future, I would like the tool to provide better integration with other tools. My company uses BMC Remedy. Integration of Jira with BMC Remedy, which is our company's ITSM tool or support tool, would be helpful. Better integration with other tools is required. I work in a large organization, where switching tools is not a rapid process owing to which getting data from one tool to another can be a cumbersome process.

I have been using Jira for four to five years. I don't remember the version of the solution. It is a tool that is configured at multiple places, so you can use it in one place, and it looks totally different in the next place, even though it may be based on the same version. I use the tool's current version.

Scalability-wise, I rate the solution a nine out of ten. It has scaled up well to meet the needs of a large number of users in different roles in our company. There are some complexities that make it a difficult tool to use. Better integration features would help with the tool's scalability.

Around 1,000 people use the tool in my company.

I received technical support from my company's internal tech team.

I have experience with some other products.

I did not take care of the product's initial setup phase, but I know it is a complex process.

The solution is deployed on an on-premises model.

I rate the tool a nine out of ten.

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.

I use Jira for project management. 

Jira is designed for issue tracking, making the process much easier than traditional methods like paper-based tracking. It is number one for agile management.

Jira's reporting and analytics features provide a clear picture of what happens, making them good. I use it in my work. 

The tool should improve its pricing. 

I have been using the product since 2006. 

The solution is very stable. I rate it a nine out of ten. 

I would rate the scalability as a ten out of ten. It's highly scalable, accommodating from just a few people to potentially several thousand without issues.

I've encountered delays and found that some of the responses from technical support weren't very helpful in resolving issues.

Neutral

We switched to Jira because it was better regarding features and execution. 

Setting up on Windows is very easy, while on Linux, it's a bit more complicated. I would rate it around a seven out of ten. It is possible to deploy it both on the cloud and on-premises. The deployment duration varied based on whether it was on the cloud or a server. If it was on the cloud, it took slightly less time, while installing it on a server took anywhere from ten minutes to an hour. 

I installed the product myself. 

I recommend Jira because it's the best tool for project management, issue tracking, and support. I rate it a nine out of ten.