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.

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 various purposes. Firstly, we use it to gather requirements by raising tickets and tracking them in the system. Additionally, we utilize it for bug-tracking. 

What I really like about Jira is that it ticks off all the boxes for any agile project. It's easy to set up, easy to use, and it has excellent notification features. Jira is the top choice for anyone working on agile projects like ours.

The tool lacks support for testing aspects, which means we often rely on integrations with other tools for testing purposes. If Jira could incorporate testing modules within its platform, it would eliminate the need for external integrations.

I have been working with the product for five years. 

I rate the tool's stability an eight out of ten. 

Jira is scalable. I rate it an eight out of ten; we have nearly 100 users. 

Installing Jira isn't difficult, but our administrator or IT help usually handles it, so I'm not directly involved in the installation process. We have around 50 resources for deployment and maintenance. 

Jira is worth the money. 

I rate the tool's pricing a five out of ten. It's paid yearly. 

My advice would be to explore the different licensing options available for Jira. There's a level of customization in pricing to tailor it to your needs. I rate it a ten out of ten. 

I use Jira for maintaining our user stories, creating defects, and tracking progress. It's a part of my daily workflow. We have a dashboard where we manage stories within sprints, see backlog items, and keep track of both open and closed defects.

Jira facilitates bug tracking in our projects. When we find a defect, we log it in Jira and assign it to a developer. Once the developer fixes it, the defect moves into verification or the QA stage. The QA team validates the fix, and if everything is good, they close the defect. If needed, they can re-assign it back to me with comments.

I like how easy it is to collaborate. We can add comments and tag specific people, which is useful for both onshore and offshore teams. Here, we can tag the person easily, and Jira updates. The commenting feature keeps everyone updated on what work has been done. Jira has a lot of versatility, which makes it a handy tool.

Within Jira, we can tag stories by the current sprint and associate them with the developer working on them. We also use Jira to track story points and progress based on status. Once a story is ready for QA, the QA team can create sub-tasks directly in Jira and start their work. 

So, Jira is great for story management, but I'd like to see better tracking of employees' daily status for improved visibility for higher-level stakeholders.

The communication features could be enhanced. While Jira sends email notifications when comments are added, it would be great to have a more real-time chat function directly within the Jira dashboard. This would streamline communication when we need to clarify defects.

Also, test case management could be more user-friendly. When we add or update test cases, there should be a better way to organize them within the dashboard.

I've been using Jira for over seven, maybe eight years now.

I haven't experienced any stability problems myself, but there's always room for improvement. So, I would rate the stability an eight out of ten. I have not faced any major issues with Jira's stability.

I would rate the scalability an eight out of ten.

Everyone uses Jira. If something isn't working, that person likely isn't working either.

I've always worked with Jira since the beginning. It is a tool 

The initial setup of Jira is relatively straightforward.

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

I would recommend using it. It's the only tool where everyone can work within a single system, and we can track each other's records. That's a tool that helps people stay aligned.

I use the solution for agile project management. We use it to break down the project into tasks. 

Jira improved our team collaboration by providing visual visibility and transparency. Everyone could see what tasks were being worked on and the progress made. The development team updated task statuses, making tracking progress and planning sprints easy. If there were any impediments or challenges, we addressed them. This process helped us track our progress.

What I find most valuable in Jira is overall architecture, especially the ability to create dashboards. This feature allows me to gain insights into my projects.

Jira's reporting and analytics features have been super helpful for me in managing my projects. I can easily generate reports and create dashboards to track progress. I can export data to Excel, making it easier to work with outside Jira. The filters in Jira also make it simple to get exactly the data I need.

The tool has been really helpful for our remote team, especially with all our scrum events like daily stand-ups. Having Jira right there during those meetings helps us discuss tasks and settings easily. Plus, it integrates with Microsoft Teams, which we've found handy. It gives us a clear picture of what everyone's working on, so if there's a lack of progress on something, we can quickly address it through Slack or a call.

The solution lacks integration with visualization tools like Power BI or Tableau, which would be beneficial for better insights.

I have been working with Jira for three years. 

I haven't experienced any performance issues with the product.

Currently, our project has a team of around 40-50 people, plus additional members from the client side who are using Jira. It is scalable. 

I haven't needed to escalate any questions to Jira's technical support. Whenever I've had doubts or needed help with something, I've usually found answers in the Jira community. 

Compared to Microsoft Azure DevOps, Jira is more user-friendly. It offers helpful video tutorials and other features that make it easier to use. One thing I appreciate about Jira is its ability to create and customise reports and dashboards.

Setting up Jira was straightforward. The online videos guided me through the process. The program is more about automated deployment, not manual deployment. I wasn't directly involved in the deployment process. Usually, it's handled by the Jira administrator. I mainly focused on my role as a project administrator within Jira.

Maintaining the tool is easy; there's no problem with it. You can even add things from your Excel sheets into Jira. For example, if you have user tasks in Excel, you can easily upload them.

Our client handles the licensing aspect. They have not yet purchased the premium version. 

We plan to integrate the tool with AWS. I rate it an eight out of ten. 

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.

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.