Jira Reviews

Pros

1. It is very flexible and fitted really well with agile development work. whether you are using kanban or standard sprint planning work flow, it supports all of those.
2. It is extremely useful to do project planning and creating stories, they will be saved in backlogs and you can access them with weight, estimate and priority.
3. It is quick to create a bug ticket to track bugs.
4. It is very easy to plan for a new sprint, by adding task, stories from the backlogs, it helps with the total points you want to target for a particular sprint, it automatically sum up the story points and make sure you don't over plan.
5. great report tool to help you analyse the project completion and nice burn down chart as well. To help the team retrospectively go back and review.

Cons

1. It is a big over complex by providing such flexible functionalities. But it is worth the time and learning curve.
2. As a developer, I don't have to pay the bill. But it is not very cheap if you have a large development team, the bills add up quickly.

Alternatives Considered

Asana

Reasons for Choosing Jira

it is a online saas. It has more functionalities and very flexible. It is suited for many different development processes. It speeds up project planning, sprint planning. bug tracking, deployment process, and so many more.

Reasons for Switching to Jira

very simple task track tool, it probably helps a small agency project that would be completed in a couple months time. With large and complex projects, or bigger development teams, JIRA is the best option out there on the market right now.

Pros

I use Jira at work everyday. It helps me organize my tasks, keep track of my progress, and connect with my team more efficiently. Jira allows me to customize my workflow, issues, and fields to fit my unique needs. This flexibility helps me to avoid confusions, and improve my productivity.Furthermore, Jira integrates with more than a thousand third-party tools, such as GitHub and Slack. This integration capability is very important because it facilitates cross-functional communications.Jira's reporting features are very essential. It allows me to monitor my progress, identify bottlenecks, and make data-driven decisions. The reports can be customized and exported in various formats.Jira helps me to prioritize work, and deliver value faster. I totally recommend project managers and company employees to use Jira at work. It helps you be more productive at work.

Cons

In my opinion, there are no cons for Jira. The only thing I can mention is that the software can be overwhelming for new users due to its rich features and complex interface. It requires some training and patience to fully utilize its capabilities. However, I do not consider this as a dislike. It is a faily user-frienly software. I enjoy using Jira at work!

Pros

Customizable Workflow, Its adaptability is its greatest asset. It enables users to customize their processes to meet the individual demands of their team. Projects ranging from simple to sophisticated.

Cons

While Jira is extremely strong, its comprehensive feature set might be intimidating to beginning users. Navigating the UI and comprehending all of the functions may take some time and practice.

Pros

Project, issue, bug, task, and workflow management are all handled by Jira software. All phases of a project's development life cycle, from planning to coding to testing, may be managed from within the system.

Cons

Problems with the software cause the window to take a long time to load, and real-time updates and app integration are also areas for improvement.

Pros

It is the greatest project management tool since it has all of the capabilities you need to construct a kanban board or a scrum board, as well as the ability to monitor all changes and issue stages with Jira. I like how we can personalize the program for our unique workflow and needs and integrate it utilizing webhooks and APIs; we do not have to come up with workarounds because it is flexible enough to be precisely what we need. I enjoy its user interface; the accessible choices and configurable dropdowns when posting a ticket make it extremely straightforward to use, and the ability to link tickets to relevant stories or test cases allows for rapid follow-up.

Cons

Almost all of the features I have discovered are fantastic, and there is nothing I do not like about Jira - it has all of the features I want, which is why it is one of the greatest project management systems and is used all over the world. However, I would like to tweak the test case management features a little.

Pros

Jira provides a ton of features in terms of project planning, the ability to create a hierarchy of epics, and feature > delivery > story, which is a great feature to track deliverables in a release. It provides sufficient options to write detailed stories, add functional workflows, excel data sets, etc. Helps in Issue and bug tracking during production support, UAT phase, and QA testing. A great collaboration platform, due to the ability to write comments, notifications, tag required personnel, and seamless integration with other tools such as Outlook and Confluence.Log efforts and Tempo (dashboard to track daily efforts) is an amazing tool for productivity enhancements.

Cons

There are a few limitations of JIRA as well - - The search engine of JIRA doesn't always fetch the correct results despite using the correct keywords, it's not as smart as an AI-powered engine or Google. Also, the Smart Query feature is not that useful, many times basic search work well.- Doesn't have the templates to write detailed documents such as FSD or a design document, not a very good knowledge management tool.

Pros

One of the things I love about Jira is its flexibility. It allows us to customize workflows, issue types, and fields to align with our specific project requirements. This level of customization ensures that Jira adapts to our unique processes rather than the other way around. Whether we are working on software development, marketing campaigns, or product launches, Jira provides us with the necessary flexibility to manage our projects efficiently.

Cons

Complexity for New Users: Jira's extensive feature set and customization options can be overwhelming for new users. The learning curve can be steep, especially for those who are not familiar with agile methodologies or project management tools. It may take some time and training to fully grasp and utilize all of Jira's capabilities effectively.

Alternatives Considered

Trello

Pros

It is a very good software to manage projects and keep a good control of the efficiency of all employees, it is intuitive to use, the customization is excellent, it reduces our errors and improves efficiency, it is the best software to drive great growth and productivity of the entire working group.

Cons

Some colleagues at first found it a bit complicated to use, but after a quick training they fully understood it and noticed that it is actually very intuitive and easy to use.

Pros

What I love most about JIRA is its robust task management capabilities. It empowers me to efficiently organize tasks, assign responsibilities, and collaborate seamlessly. With JIRA, I can track and prioritize tasks effectively, leading to improved project success and enhanced team productivity.

Cons

What I like least about JIRA is its steep learning curve for new users. Initially, navigating through the various features and setting up workflows can be overwhelming. However, with time and practice, it becomes easier to harness its full potential for efficient task management.

Pros

What I like most about Jira is its ability to provide a comprehensive overview of project status and performance, through its customizable dashboards, detailed reports, and agile boards.

Cons

While Jira is a highly effective project management tool for software development, its downside is that it can be complex and overwhelming for new users, requiring a significant learning curve to master.

Pros

I really like the level of detail and control you can have when it comes to team planning. When the cycles begin, when they close, the stages and hierarchies that can be built within the same project or task. I consider that for projects that require a great level of detail it is extremely precious and necessary to leave nothing to chance.

Cons

Although I value all the level of detail that can be indicated for a task / project, when simpler tasks are required, follow-ups, daily operation, the little flexibility of the tool becomes totally annoying to ignore some unnecessary parameters. On the other hand, the responsibilities of the tasks always fall on a single member, which can generate an imbalance in the measurement of team performance, as one person is probably left with many more activities than others. What bothers me most from day to day is that on the activity board every time a card is moved to another column (example from "To Do" to "Doing") the board does not update automatically but it gives you an annoying signal It is not updated and until you refresh the page it will not allow you to move that card or any other, it will continue to show you "board not updated", this really makes the tool a little agile for larger teams and with precise and short follow-up meetings.

Pros

Jira is a very good platform for organizing your team and projects using Agile/Scrum or Agile/Kanban. Whichever option you will choose you are covered! With its extensible platform through plugins you will never get tired of Jira. The installation is pretty much straightforward and with latest versions you can also make it HA, for instance on AWS, quite easily.

Cons

Although the product is very mature, feels also like a big giant monolith although its plugin architecture. Also, plugins are too much expensive for just simple features. There should be much control from the Atlassian Marketplace, which should follow more an App Store logic like Apple's or Google's one.

Alternatives Considered

Pivotal Tracker and Trello

Reasons for Switching to Jira

Jira is way more famous and most of the Agile coaches working in the field, are already aware on how to use and customize it, based to their needs.

Pros

Coming on board with Delta I hadn't user the JIRA platform outside of submitting tickets in my past. There was a shell created by our IT team and it was a great start but with the help of an intern he and I were able to completely change and enhance the user experience on both sides for those who enter tickets and those who work or engage with tickets.

The system seems a little overwhelming at first because it offers so many variations however once you really consider what you want to do and who you want to achieve it really straightforward.
You're able to change and modify just about every aspect of the interface so that its complete company-specific or even department-specific is you choose. You can make it look like its an extension of your companies actual website.
You can access and run reports for so many different KPI's or metrics to see preformance or SLA's and they are all realtime.

Cons

Like I stated it was a bet overwhelming bacause there are so many options and changes that can be made using JIRA however there are tons of resources as well.

Alternatives Considered

Salesforce Sales Cloud

Reasons for Switching to Jira

We chose JIRA because it appeared to be the best application for what we needed. It was also expandable and we could scale it as needed in the future. We also like that it was completly customizable.

Pros

Jira is a nice and powerful tool to track our projects. This includes all Epics, Stories, Tasks, Sub-tasks and bugs. It allows for many options as well, including labels, easy prioritization (drag and drop). Recently they have added features to help track milestones, so you don't need MS project anymore. There are a lot of different reports (good for clients) and numerous integrations available.

Cons

After you get to so many users, the costs increase quite a bit. Confluence and some add-ons are also additional costs. We have also found the odd bug. For example, the wrong ticket is updated, or in the backlog view the mouse curser can no longer select rows (fixed by a refresh). Classic Projects vs. New Project is also a bit confusing. It's hard to get new features for some of our old projects, unless we recreate the Project from the start.

Alternatives Considered

Trello, Microsoft Project, Basecamp, Wrike and Asana

Reasons for Switching to Jira

We chose Jira as our team has experience using it already.

Pros

I have been using Jira from last 5+ years now for Backlog management, Requirements management, Bug tracking and creating Dashboards for project review meetings with leadership. It's extremely flexible tool where you can configure your own workflows and customize it as per your project's needs. It's my go-to Agile project management tool (especially for Scrum). It's so easy to create and manage user stories, bugs, technical tasks etc. You can tag your user stories as per Epics and Features, you can also add labels to each ticket. You can track the status of any ticket and also see the bandwidth allocation of various teams. In JIRA, you can add advanced search filters to view only those user stories that has particular combination of fields (like specific assignee, status, epic name etc.). Moreover, JIRA Dashboard provides a bird's eye view of the overall project status which gives the real time visibility to you and the leadership team.

The UI is very clean and simple and it makes Agile Development very productive, once you get the hang of it. Plus, it's very well integrated with many popular apps like Google workplace, workday, slack etc.

But there is definitely a steep learning curve with Jira. The success of this product largely depends on how your management/leadership standardize various processes and workflows within Jira.

Cons

Jira doesn't allow you to add multiple assignee on one user story, and this becomes a concern when multiple developers are working on one story.

Also, it's hard to get support from Atlassian when you are facing some technical issues.
Additionally, in my experience, I have found that as Jira provides great level of customization, it can become really messy, if multiple management styles are involved during project planning phase. The workflows can get overly complicated and as a Product Owner, you find yourself stuck in updating the ticket statuses all day long.

Pros

The fully integrated task and project management boards with extensive levels of detail to run Kanban maintenance boards, complex sprints and even visualise recruitment pipelines. In collaboration with Confluence and BitBucket, the Atlassian product suite make the management of a growing software team seem easy.

Cons

JIRA has quite a steep learning curve for less software native users and can appear too complex for the average operational or commercial person. As such, it can be difficult to convince new people to use JIRA without extensive training and hand-holding. This could be improved by guided tours and a simpler interface for "new starts".

Alternatives Considered

monday.com

Reasons for Choosing Jira

Asana did not offer the same ease of use when it comes to segmenting projects, running sprints or handling issues. JIRA was much better suited to an agile, fast-growing software company with beautiful Gantt chart and roadmap visualisations that were game-changing for overall project coordination.

Switched From

Asana

Reasons for Switching to Jira

JIRA had more detail and was scalable in comparison to Monday.com or ASANA. The ability to flip between Gantt charts, Kanban boards and sprint backlogs made it ideal for a multi-faceted ream. The detail provided in each task/issue card is fantastic with room for various integrations, such as Confluence pages and Slack notifications, made JIRA a no-brainer.

Pros

I will give an example of how I used it on one occasion and the advantages of having had this software.I was hired by a digital marketing company to improve proprietary applications, internal APIs, creation and migration of landing pages made in WP for our clients, migration of PHP applications to Python, server management, diversity of containers... The DevOps who was doing all that work left the company.An external audit was hired that provided workers spread all over the world, Spain, India, Latam...So we find ourselves with a lot of work, from very different areas, work environments and projects of all kinds and just one person to manage everything.With Jira we all worked under the same environment to organize tasks, but above all incidents and bugs, and with the need to manage the priorities of each new element that entered our work boards.At a glance, I could assign tasks, review code, refactor or modify it, and upload it to the test servers. Review the tickets, with screenshots of the errors or the new results that should be obtained. Keep in touch with everyone from one place and also receive all feedback in Jira.It was months of hard work, without Jira it would have been impossible to manage it.

Cons

Despite having Jira with everything necessary for software development, sometimes it becomes more complex and less visual than if we accompany it with some extras, also from Atlassian. So it is easier for some boards or planning to use Trello, GitHub or Bitbucket for continuous integration, Sourcetree to make the different branches and versions more visual, Composer for team collaboration...

Alternatives Considered

Trello

Reasons for Choosing Jira

It is expensive to maintain and you never get the ease of use and tools of software of this quality.

Reasons for Switching to Jira

It is more complete for incident management, priorities integrates better with other solutions

Pros

I've been using Atlassian products, JIRA in particular, for over 12 years. It's come a long ways in this span in terms of advanced functionality and additional configurable content, and it's consistently proven itself as a market leader in project and task management services. JIRA reporting, dashboard, task tracking, and project development activities are comprehensively impressively designed, easy to use, and highly collaborative for internal teams.

Cons

The success an end user will yield from the software is highly dependent on it being configured in a manner that aligns with the business needs of the customer organization. For example, I've experienced instances where there are growing pains in how internal teams learn to standardize the way they tag tickets for project and task tracking and then use these identifiers to develop reports, create dashboards, and track schedules. If not setup properly by System Administrators then the ROI will be delayed, making it essential for teams to be properly educated and trained on the system. JIRA provides a wealth of content for training & education but worth noting the difficulty an organization can face if not approached strategically and with strong design plans during the discovery phase of implementation.

Pros

Jira is *incredibly* versatile. You can customize almost every aspect of your Cloud instance, Project, Boards, & Workflows to fit nearly any use case, and across multiple departments.
Permissions to your Jira instance can be restricted at a very granular level if need-be, but can be more broad if the occasion calls for it.
Additionally, and probably the largest reason we transitioned from enterprise Jira to a Cloud Jira instance is the pervasive availability of integration across the market.
Speaking of market - Jira has a growing 3rd-party market that offers enhancements to the Jira platform that Jira does not natively provide or are too complex for an untrained Jira administrator to script themselves. Of those that are "approved" by Jira, we are extremely happy with the breadth of functionality, integration and ease of use.
With all that I do have to say that our favorite thing with all project leads is Jira Automation. Once you understand the "SmartValues" language that automation runs on, the use cases for automation are truly endless. It is one of the many strong features from a project management perspective.

Cons

Jira takes a village. Atlassian has an incredible resources in the "Atlassian Community" and they do a great job of having experienced users there to answer questions but, because each instance can be set up so differently, the actual customer support request portal is limited to bug fixes. As a result, much of my time administering Jira is spent researching how to fix a roadblock or how to modify permissions - a lot of "learning by doing". Generally speaking, Jira can be difficult to use from an administration perspective, *but* for the purposes of moving ticket along, the UX is pretty good and the UI is fairly intuitive.

Pros

JIRA gives me so much functionality out of the box. Within five minutes, I can create a board and invite my whole team to start working with me. It doesn't take long to customize your presentation of work to make it specific to your business. It has become the standard for the industry and with good reason; JIRA gives me everything that I need to track performance and ensure a timely release.

Cons

There are occasionally some annoying bugs that will present themselves, but it's never something that really prevents me from using the product effectively; usually it's an annoying UI bug that looks messy or ugly. For the most part, many of the people that complain about the product just don't know how to use it 'as is out of the box'. The more configurations you try to make, the more problems you can create for yourself. Aside from this, their customer service is quite lackluster and it often takes days if not weeks to hear back from support - usually the bugs are fixed before you even get a response.

Pros

Flexibility in workflows and tracking separate projects and sub-projects in the same system.

Ease of creating multiple tickets as well as placing them into different projects without having to be in the projects portal.

Creating reports to review metrics is relatively easy, it was useful in an integrated project to review estimated times reported in previous sprints to project development times for other projects.

The flexibility of how tickets look and editable fields as well as workflows to tailor to the team and/or project being worked on.

Cons

The bad part of Jira's flexibility is that settings are all over the place and you typically need to refer to Jira's knowledge base on how to configure custom settings whether it is for fields inside of tickets, workflow settings and automations, and many other settings.

The standard Jira end user interface is not exactly user friendly and some things may not make sense depending on the team using it such as a ticket being in a closed state however the resolution state has separate "states" such as do, don't do which is more used by software development teams.

Jira typically requires a lot of customization when setting up new projects either for project managers, agile software development teams, or integrated project teams. As an administrator this can be difficult to convey to my end users who want to track their projects in Jira. This is where you need to have great communication with your end users to be able to setup and tailor the Jira project to their needs and improve the overall Jira experience.

Pros

Jira is the most powerful and popular project management tool available. The best thing about Jira is its high customization capability and simplicity out of the box.We are using Jira for more than 7 years, In any organization, I worked with, I have seen Jira.Most useful features for us in Jira - 1. Customization is very powerful in Jira. For almost every specific need as per the particular project, we were able to customize Jira.2. Powerful reports and dashboards - Easy visualized graphs and charts help us to recognize the current status and health of our progress. It is very easy to track time, individual user performance, blockers, and progress of the sprint.3. Extensive - It is very extensive, even for the rarest need there is already a plugin available we can use out of the box.4. Collaboration and communication- It is the best thing in Jira, no more dependency on Emails, and no more wasting time on checking and finding scattered information in the mail. Jira provides transparency in communication, all communication is in one place. Even having the related important documents, versioning of documents is available.5. Integration- its integration is beyond any other available tool. We are using Confluence to manage all the related documents in one place, and versioning is very easy, We are also using git bitbucket, TeamCity CI-CD integration in our project which made our life super easy.6. Agile tools- Out of the box we can jump-start with premade templates of

Cons

The only con I see in Jira is that it went a little complex to configure as an administrator. But it is obvious due to its large extensive and customizable capability. It happens only for the initial time but that issue can be copped as it has a very vast help community and forums.

Pros

Couple of features below that I really admired the most-Mobile version of Jira board, colorful status tracking with accurate percentage, effective customized workflow modal, quick peek view of tasks in dashboard, search option for any filter, quick catch for getting user by using '@', easy query handling and filters, easier mode of cloning tasks, linking items and referencing, multiple built in report types like bar chart, pie charts, etc., Kanban & Agile flexi boards, vast of plugin support like git-hub, git bucket, zendesk, etc., From the admin point - easy configuration of development tools dotnet, configuring mailing options, deep level view of audit logs, watch list for issues.Couple of features below that I really admired the most-Mobile version of Jira board, colorful status tracking with accurate percentage, effective customized workflow modal, quick peek view of tasks in dashboard, search option for any filter, quick catch for getting user by using '@', easy query handling and filters, easier mode of cloning tasks, linking items and referencing, multiple built in report types like bar chart, pie charts, etc., Kanban & Agile flexi boards, vast of plugin support like git-hub, git bucket, zendesk, etc., From the admin point - easy configuration of development tools dotnet, configuring mailing options, deep level view of audit logs, watch list for issues.

Cons

Sometimes I feel, the JIRA GUI is clumsy to have many things in dashboard, other than that I do not see any specific negative factors to hate JIRA, and it depends on how we use the features for projects.

Pros

It comes with a ton of functionality by default. It contains several levels (Teams, Projects) that may support the structure of the entire business, creating just the correct amount of separation while also allowing for the proper linkages between the various teams inside the business. May be easily integrated with the entire Atlassian ecosystem (Bitbucket, Confluence), and I highly encourage doing so because you'll have a ton of places to store any piece of your project (code, backlog, sprints, documentation). It provides you with all the tools you need to manage any Scrum or Canvas team, albeit I must stress that you will benefit more from adopting Scrum. It makes for incredibly inventive automatic build ticket systems and is simple to incorporate via code.

Cons

It's expensive and difficult to say whether it's the best tool for tiny independent teams when there are many free choices available that can manage numerous users. That is in fact the best option for businesses, but for low-budget teams, it's definitely safer to use a free alternative with no membership cap.

Alternatives Considered

monday.com

Reasons for Switching to Jira

I adore how straightforward the program is.

Pros

Jira is highly customisable, and also has plugins. It allows you to monitor your projects and provided granulated access to individuals. You (or your admin) can set roles for the project and associates those roles to certain activities and then associate the roles even further to individuals.

You can organize your tickets in sprints and releases as well as monitor workload and task assignment to your team during sprints (or whatever other form of software delivery you wish to choose).

Cons

Pricing model. Currently, you have a choice of server vs cloud setup. If you have a team that can maintain the server instance, I'd recommend going to server because you have a lot more plugins you can use on server and you can set it up the way you want. The best thing is the licenses are a one-time cost, as opposed to lower, but monthly and forever costs on the cloud portion.

The other thing that is to be considered is that the plugins you choose need to have the same level of range for hte user count. i.e if your jira is for 101-250 users, all your plugins will need a license level of the same range, i.e 101-250 users. Something to consider if you are thinking about moving to Jira.