Jira Reviews

In our organization, we use Jira for project management and usually use the Scrum project type. We might adjust the workflows and stages to better suit our needs, but we mostly use the default functionalities it offers to manage our projects.

It's flexible and customizable, and we frequently use it with customized workflows and dashboards to track defects. Jira works well with tools like TestRail and Clarity, which help with test management. It has various APIs.

Jira's reporting and analytics features support project management by providing useful out-of-the-box reports. These include burn-down charts for Agile project management and various other reports. These default reports typically cover around 60 percent of users' needs. Users can customize their reports and dashboards for the remaining needs, which usually fulfill about 80-85 percent of requirements. Add-ons can be used for the remaining small gap.

The tool mainly supports remote or distributed team collaboration through its cloud version, accessible from anywhere. Within Jira, you can communicate effectively with team members by assigning issues, leaving comments, and referencing people for notifications. While direct communication features within the tool are decent but not outstanding, integration with tools like Slack or Teams can enhance collaboration further.

Jira could be easier to use, especially for administrative tasks. It's quite complex, so it's important to understand it well. While the reporting and dashboards are good, there's room for improvement in some areas where extra features would be helpful.

Sometimes, we need add-ons in the product, especially for reporting. While you can get these through add-ons, they can be pricey. The licensing system for add-ons might also seem unfair because you often have to pay for all users, even if only a few use the add-on. So, maybe the licensing model could be adjusted.

I have been working with the product for ten years. 

I rate the tool's stability a nine out of ten. 

We've never had any issues, even with up to 2000 users. However, scalability can be limited by the license type. I'd rate Jira's scalability as a ten out of ten.

The tool's support is helpful. 

For deployment, setting up the tool takes minutes. Implementing additional configurations like SSO or integrations might take half a day to a day. The time spent configuring and customizing screens and workflows depends on your specific needs. I usually take about three or four days to complete everything.

The licensing cost for Jira is typically around seven dollars per user, though it may vary depending on regional variations. This cost is for a subscription-based model rather than a one-time purchase. I rate its pricing a seven out of ten. 

I work across multiple projects, so people might approach me for support when needed. I would recommend Jira to other organizations. For inexperienced users, I would advise seeking help from experts if there's something you can't do in the tool. They can customize it to fit your needs. Overall, I'd rate the product an eight out of ten.

The solution is used for project management and agile software development. It is also used for general business planning. We can use it for any small or large project. The tool is designed to do sprints and Kanban. It was built for Agile. It works well for any Agile-style project.

There are various versions of Jira. Help desk process, using ITIL, planning a new product from scratch, marketing, task management, and team management can be done in Jira. We use automatic print preview settings and visualization of the progress. We can link all of our information in Jira into Confluence to do live meetings with live data. We have a lot of templates in Confluence for any business or team meeting we need.

The reporting and analytics features make it easy to calculate team velocity. We can track time and effort. It's very easy to generate burn-down and burn-up charts for Agile teams. It also has many useful automatic charts for help desk services. I haven’t used it much, though. We can integrate a lot of tools with the solution.

A lot of companies use a mix of Waterfall and Agile methodologies. They often need more individual metrics for time and cost tracking. Many larger companies would like to have more resource management within Jira. The model for adding features is by application. If we add an application to Jira, we must pay for the licenses for everybody on our contract when only a few people need to use the application. Adding applications is very expensive. We cannot make it for only the few users that need it. We must buy the application for the entire workforce that's using Jira, so it's not very flexible.

I have been using the solution for three or four years.

Overall, the product is stable, but it has had some security problems and a major outage in the last couple of years. It's something to be aware of, but I don't worry about it that much.

The product’s scalability is pretty amazing. I've seen customers with over 10,000 users, and it works well. I don't have a lot of scaling needs. However, it's super easy to onboard new people. And I've never had to worry about running into performance problems. We just add the people, and it works.

If we are starting a project with a small team from scratch, we can have Jira up and running in about ten minutes. The deployment process is logging on, adding the users, and hitting the start button. It's very easy. The tool is deployed on the cloud. I recommend the cloud. It is usually better and the easiest.

The ROI is excellent for the cost of the basic product. It has so many features and integrates with so many things. There are a lot of useful free apps available. We can really improve our project management and task management at a low price compared to buying a bunch of other products. It's very flexible. We can adapt it to different kinds of projects. We can adapt it to the way the teams need to do the work instead of having to learn the rules of the software itself.

I use a monthly subscription. We can opt for an annual subscription if we go through a reseller.

I tried Asana and Trello. I chose Jira because it integrates with many other applications and easily expands with its own apps. The integration within the Jira, Confluence, and Atlassian products is automatic. We don't have to spend time linking information and data. We just need to install it, and it will be ready to go.

I haven't used a lot of direct integration with Jira. I've seen it used with code repositories for continuous integration and continuous deployment. It's really fast. Everything is automated and very easy to set up. I haven't used all of the features. I would definitely recommend Jira. My advice is to use the online resources on the Jira home page. There are a lot of people who will help you set it up for free. We can avoid making a lot of mistakes by using the community advice. Overall, I rate the solution a nine out of ten.

We are using Jira for scrum, specifically for Agile Scrum. Most of the tasks are in Jira, including the dashboards and reports.

For now, we are using Jira for the scrum. We are quite happy with this as it allows for task management and report generation.

We can query the tickets and create dashboards based on these queries. This functionality is helpful for monitoring project status and tracking bugs. We are using Jira for scrum within the Agile framework. Tasks and dashboards are in Jira, which also assists in report generation.

I am unable to query based on the subtask and link by issue, which can be improved.

I have been using Jira for more than five years because my previous company also used it.

For stability, I would rate Jira as eight out of ten.

For scalability, I would rate Jira as seven out of ten.

I have not contacted Atlassian's technical support since another team handles these issues.

Positive

I have tried Trello, which is open-source and free, however, Jira is much more powerful.

The setup of the project in Jira is handled by our scrum master, who is not a very technical person, yet manages it efficiently.

For small companies, Jira is not affordable, leading them to use Trello or other free software. Jira is quite acceptable for medium to enterprise-level companies due to the features it offers compared to its pricing.

I have not used Asana, but I have used Trello. I find Jira to be much more powerful.

Overall, I rate Jira eight out of ten. I am quite content with its features and capabilities.

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 Jira to schedule tasks, customize them, and track progress within sprints. We follow a two-week sprint structure and manage all our tasks within Jira accordingly. We use it in the defense industry, and our applications are related to satellite communication. 

I have experience with Jira's bulk tracking and issue management. We use it to add new features to our product, fix bugs, and address customer feedback.

The features I find most valuable for work and team productivity are creating subtasks and tracking their completion. Additionally, reporting features such as burnout charts and task reporting are quite valuable for us. 

The tool's integration capabilities with other tools are quite nice. It's an open tool that easily integrates with third-party products like Microsoft Project and GitHub. Integrations work smoothly; we've also integrated it with requirement management tools per our needs.

Improvements in Jira for the next release could include adding AI tools for dashboarding, making it easier to report insights, and enhancing business intelligence capabilities. It should also improve on-prem support. 
As far as I know, Jira's on-premise support is being discontinued. From last year onward, they stopped providing on-premise licenses and now only offer cloud support. This shift happened gradually, and I believe they now only offer cloud licenses.

I have been working with the product for ten years, since 2014. 

My company has 200 users, of which nine to 10 are from my team. 

The documentation and the internet are enough to clear our doubts. 

Positive

The tool's deployment is easy; I rate it a nine out of ten. It can be completed in two to three days. 

The tool's pricing is expensive. The new pricing is indeed quite expensive compared to what it was a few years ago. Last year, when we intended to renew our subscription, we found the pricing considerably higher.

The decision to use Jira on-premise instead of the cloud is primarily driven by security concerns, especially in industries like defense, where sensitive information must be protected.

We want to continue using the tool, but we may have to explore other options due to the lack of on-premise support and Atlassian's emphasis on cloud deployment. If it extends its support for on-premise usage in closed network environments, we would gladly continue using it, considering our current investment and experience with the platform. However, if no such support is provided, we may need to evaluate alternative solutions that can be deployed on-premise.

I recommend using Jira because it's easy to work with and open, allowing for integration and development of additional features if needed. Its ecosystem is vast, with a large community worldwide using Jira, and it offers many add-on products for various needs.

I rate the overall product an eight out of ten. 

Jira is used for field management and task assignment. We use Jira on the project management side. We also use storyboards for planning and scheduling. It can be used for tracking and managing issues. It provides a dashboard showing what's open and what's closed. We can access all these details there.

The easy tracking feature is available, but it serves as the foundation of Jira within the bundle. Apart from that, the software supports individual development and testing with LiveStack. Previously, we use Insight to identify additional defects, which could be related to multiple test cases. A single defect might encompass multiple test cases, and vice versa, with different defects linked to various test cases. Having a separate defect management system would allow for one-to-one, one-to-many, or many-to-one mappings. We are unable to perform all of these tasks with the current issue tracker.

The integration of other open source tools with Jira is very useful. It allows us to create documents and transcriptions, making it versatile beyond software development. Jira was originally developed for IT projects, but it can also be effectively utilized for non-IT sectors. It enables tracking and maintenance of projects outside the IT domain as well. I recommend the solution.

The reporting feature is very beneficial. Customers can report using the predefined report template.

The workflow is fine, but it's only integrated within Jira and not with other tools. Additionally, the SQL query is also very helpful.

In project communication, it is necessary to train every new member who joins us for Jira. Apart from training, using Jira for project planning and scheduling can be very helpful.

Remote collaboration is helpful. We need to conduct screen sharing sessions with everyone, it would be even better if Jira could provide integrated screen sharing capabilities and enhanced email communication features. Therefore, the release of a MailServer feature within Jira would be beneficial.

If I want to create a Jira account, I need an email ID. If Jira will provide the same functionality as Gmail, such as a mail server, then collaborating via Jira email will be possible. Additionally, for trained individuals, we can share screens within Jira itself.

I have been using Jira for over 5 years.

The product is stable.

I rate the solution’s stability a 9 out of 10.

We have three member along with a founder and co-founder using this solution.

I rate the scalability a 9 out of 10.

The initial setup is easy but if any new ecommerce is coming into picture, it can be difficult.

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

We are using for free version. The pricing is very cheap and has a very nominal fee.

Overall, I rate the solution a 10 out of 10.

I have managed various projects using Jira, including tasks for the government, the environmental sector, education, and donation applications. I have also worked on multiple websites for marketing and search engine optimization.

The most valuable feature of Jira for sprint planning is the timeline feature, which allows for better visualization and planning of releases. However, there are limitations compared to other tools like TFS, which offer more flexibility with features like user stories, epics, and initiatives without extra fees. Despite this, Jira's ease of adding user stories to sprints and connecting them to releases is very good.

Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist. In TFS, it is simpler to manage capacity and reassign tasks when necessary. Additionally, a feature in TFS automatically creates relevant tasks based on a code snippet linked to a user story, saving time and effort in task creation. This feature isn't available in Jira, which makes task management less streamlined.

I have been working with Jira for almost two years.

Jira is expensive.

I recommend Jira for its usability, especially for writing user stories and adjusting metrics, though it is expensive.

Jira has improved our team's productivity mainly through integrations, particularly with Slack. This integration helps keep track of changes made to user stories, providing alerts for any updates. 

I would recommend Jira for managing projects in agile environments, but certain features are necessary for better functionality, like improved capacity calculation and streamlined task creation. Additionally, Jira can be expensive, so essential tools like test planning should ideally be included in the standard subscription rather than requiring costly third-party plugins.

Overall, I would rate Jira as a seven out of ten.

We are using the solution for project management.

The solution helps to track issues related to project management. It helps with different activities like assigning tasks and reacting to issues.

Linking the issues to members in the team and outside the team has been valuable. Jira's reporting and analytics features are very important for analyzing the entire sprint activity at the end or middle of the sprint. The tool helps track the capacity, velocity, assignments, and different team members’ activities. We can track the entire sprint speed. The burndown charts help track projects. Over time, the tool has completely adapted to our project's scanning needs. We use it however we want and change the settings as we want. So it's quite adaptive.

The product must provide more automation. Scripts should be more readily available for implementing projects. It should provide quick launch features to build projects.

I have been using the solution for three years.

I rate the tool’s stability an eight to nine out of ten. It's quite stable. We haven't faced any issues.

The tool is quite scalable. It was quite useful for our projects. I rate the scalability eight out of ten. We have 30 to 40 users. We use the product daily.

I have used Azure for some projects. We switched to Jira because it is easy to implement and use. It is good for smaller projects. It is easier to start using Jira than other products.

The initial setup was quite easy. I rate the ease of setup an eight out of ten. The product is deployed on the cloud.

The price is quite competitive. I rate the pricing a seven to eight out of ten.

I will recommend the product to others. It is easy to use and implement. Overall, I rate the solution a nine 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.