Jira Reviews

Pros

Jira has great project tracking and management features and is quite customizable. The agile boards make work management and sprint tracking easy, and the interaction with other programs like Confluence and Bitbucket is flawless. In addition to that, we can design intricate workflows that are particular to the needs of the company.

Cons

Particularly for new users, the learning curve can be quite hard. Because there are so many features and options accessible, the UI might occasionally feel overwhelming and take time to get familiar with. Furthermore, the cost may be prohibitive for startups or smaller teams.

Pros

Good connectivity between items (epics, user stories, and so on).
Overall, it serves the basic needs of R&D management and collaboration with products.

Cons

Comnersum, many simple activities have bad UX and are hard to use quickly. The filters are not intuitive, and the navigation between different screens is not apparent.
The UI looks old.
Lack of many capabilities that would make product managers' work easier.

Pros

Once it is properly configured it works well for product management

Cons

To Configurate the Project, Boards, Workflows, etc. is very complicated and some actions take a long time to reflect changes.

Pros

Features such as Scrum boards, kanban board, sprints, and backlogs are great for teams who follow agile methodology. We can customize workflows, fields, and issue types as per our needs. Most important feature is that it enables us to track the project progress in realtime. In addition, it is compatible with many external apps and facilitate the smooth workflow.

Cons

Extensive features and customization options can make the initial setup complex, especially for newcomers to project management tools. Its lacks built-in idea management functionality, we need to use some additional tools for brainstorming and concept development. Also, the pricing seems to be bit high and it may not be an affordable option for small teams or startups with limited budgets.

Pros

I like that despite is a big team or small team, it has a lot of features that help tracking the work, and with little customization you are ready to go

Cons

Sometimes por the product managers is a bit complicated to do things the right way, but I would say is more like they didn't investigate the tool more than a jira fault

Pros

It was pretty quick to get started and using the tool. Not a huge learning curve for the basics, but need a bit more training for taking care for some of the more advanced features.

Cons

Lot of features, many of which I haven't really learnt to use. It also had a large collection of add-ons but not many of these are free and so additional costs can be incurred.

Pros

Jira facilitates team collaboration by allowing us to prioritize projects and issues, track time spent on them, and use the comments area. Dashboards provide a high-level understanding of the project's status. Different statuses, such as new, resolved, testing, and fixing, are displayed to indicate the current stage of the issue.

Cons

From my experience, I noticed that the fundamental UI/data structure is slow and lacks context. It is slow to use and has low acceptance rates across the workforce.
Supervisors may log items in the system but continue to run Google Doc spreadsheets for tracking in parallel, resulting in data fragmentation. That, to me, proves that it is unsuitable a little for the purpose we need it for.

Pros

the issues filter make life so easy and the tempo app is great for tracking hours

Cons

the settings are a bit dogmatic and email set up has issues

Pros

It's nice to have a tool that keeps user stories, documentation, and code all intertwined.

Cons

The jql can get a little complicated for folks who are not technical.

Pros

Its backlog feature really makes it easy to plan sprints.

Cons

The onboarding experience wasn't great. It could take some time to get familiar with all its powerful features.

Pros

The biggest strength that Jira has to offer is how customisable the app is. We're forever fine tuning how how development flows are setup and I've never run into an issue where what we wanted to achieve could not be possible. The workflow editor is pretty straight forward once you figure out how to map these to specific projects and features.

It also has a mammoth number of apps that can integrate with it, which can greatly help simplify your organisations stack. We use a bunch of apps that connect to Jira such as Slack and Git.

The mobile app is pretty good and more simple to use. There's also a new iOS app that you can run on a mac that seems to be a slightly faster and more user friendly version. However, I haven't quite worked out how to tailor the notifications.

The search is very powerful!

Cons

It is very slow to load pages and jump between stories. When using this on a daily basis it really gets annoying.

When we need to change a setting it's hard to work out where to go. I have to say I've never seen another app quite like Jira which has so many different places to go to in order to change very similar settings.

If someone accidentally creates a ticket with the wrong type the only way to change it is to Move the ticket. And I can't seem to change the status of the ticket at the same time. So often an Open bug ticket becomes an Open feature ticket, which really should still be in Draft.

Alternatives Considered

Trello

Reasons for Choosing Jira

We hired a new Head of Development who encouraged us to make the switch as Jira had better reporting/time tracking features.

Switched From

Pivotal Tracker

Reasons for Switching to Jira

Although it was more simple to use it didn't have the time tracking and reporting features we needed.

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

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

If you are looking for a management system that is good enough to cover all your needs then Jira and the Atlassian portfolio is exactly what you are looking for. Every aspect of your workflow is infinitely customizable and perfectly integrated with their entire suite of software development tools. Once your setup is complete everything is easy and automatic for your team. The potential for boosted productivity is huge.

Cons

All the updates can be overwhelming. Great updates can provide users with additional features without affecting present ones but some updates are breaking and requiring you to find the relocated setting in order to configure what you want. That is adding to the already high cost of setting up a new project. If you have someone dedicated to administration then the rest of the team will have a great experience. This is a very powerful tool and that means it will take time to learn and properly manage it.

Alternatives Considered

Basecamp, monday.com, Wrike and Asana

Reasons for Choosing Jira

We simply outgrew Trello. If you require an easy and quick-to-set-up solution that will get you started within the hour then Trello is for you. Jira is the natural next step with easy migration and a similar workflow. It takes more time to set up so the question is whether you need the additional features. The only thing I am missing from Trello so far is the smooth keyboard shortcuts.

Switched From

Trello

Reasons for Switching to Jira

I was already invested in other Atlassian projects like Trello and Bitbucket. Better integration with Bitbucket was the deciding factor. The overall more developer-focused image and development tools available also contributed to the decision.

Pros

It's a very powerful tool. It provides many advanced features to collaborate with people. We can easily tracks things on Jira through our mobile devises and other gadgets. It helps us to plan the projects with tasks and sub-tasks.

Cons

It is an expensive software compared to other open source software. I have worked with many software Jira is one of the most expensive product that we have used in our projects.

Alternatives Considered

Salesforce Sales Cloud, Asana and HubSpot CRM

Reasons for Choosing Jira

Salesforce was not suitable for our requirement and the type of business that we are doing. So, we have shifted to Jira and it's a very important decision for us to collaborate our exciting team.

Switched From

Salesforce Sales Cloud

Reasons for Switching to Jira

Jira is developer friendly, easy to work with, easy to collaborate with multiple people on the same task, have features to same attachments and issue tracking with notifications is very helpful to complete tasks on time.

Pros

The service which is the Cloud version is just as you would expect from the Helpdesk Type system. You have the ability to manage permissions to what access users have. You have plenty of third-party integration options. Also, one of the most important services is the ability to integrate Azure SSO.

Cons

One of my pet hates with this service is the tickets themselves in that on some tickets their comments can get lost in that the system starts to hide the older comments so if you are in a rush to get some info you need to unhide those comments

Alternatives Considered

ServiceNow Customer Service Management and ConnectWise ScreenConnect

Reasons for Choosing Jira

We moved from the application due to the number of other third parties needing to get involved. The Jira is widely used so we decided to move the Project-Based tickets into a Cloud-Based Jira system. There was also a cost involved.

Switched From

ManageEngine ServiceDesk Plus

Reasons for Switching to Jira

We have used the On-Premis version of Jira in the past plus most of the Third-Parties we are dealing with also use the Jira Cloud Platform

Pros

1) Integrate seamlessly with development tools like Slack, Github, or Bitbucket.
2) Workspace is very configurable; you may customize the components of each task on your board, as well
as create your own icons, labels, and automated processes.
3) Connect all issues/tasks to Epics and view the anticipated outcomes in the Product Roadmap.
4) It offers the flexibility of a kanban board, which provides the user with a clearer view of what has been accomplished, what is in process, and what remains.
5) User story statuses may be used to monitor progress and control workflows.
6) Allows for bulk import of epics and user stories, which speeds up administrative duties if this information was previously recorded in another format, such as CSV.

Cons

1) Only internal users may be allocated to tasks and user stories. This might result in unnecessarily long delays when external users want immediate input or participation.
2) When many boards exist within a project, statuses (user stories) cannot be established explicitly for each board.
3) User stories may be assigned to just two categories of users: assignees and reporters. JIRA does not permit the assignment of numerous assignees to a single user story.

Alternatives Considered

monday.com and Smartsheet

Reasons for Choosing Jira

Jira was more cost-effective and better for us because it met our needs more. It worked better with other Atlassian products that we were going to buy. So, it's clear that Jira is the best modern Project Tracking tool on the market right now.

Switched From

Trello

Reasons for Switching to Jira

Because Atlassian has a lot more products, they were able to keep everything under the same roof. When we used JIRA integrations with other tools, they worked really well at the time and were very useful.

Pros

Jira allows us to efficiently manage a tasks across a wide variety of different projects, assigning work easily to each team member and allowing us to run a clear process from briefing through quality checking. It has allowed the team to communicate more effectively and improved the overall quality of delivery with better expectation management.

Cons

We've used a variety of different task and process managment tools in the past - and still do for direct client work where they have a preference (e.g. Basecamp, Asana etc), and the interface on Jira is maybe not as attractive, but it works fine and allows good interaction.

Alternatives Considered

Trello and Asana

Reasons for Switching to Jira

We've used a variety of different task and project management solutions with clients in the past, but Jira proved to be a better fit for us as an organisation, primarily because it was better suited to the size of our team and the number of projects we were working on.

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

- Manage multiple projects under one project in JIRA and works well for a complete program
- Email notification when any changes made in JIRA makes collaboration efficient
- JIRA board (Scrum Board) in JIRA and defining specific project JQL to filter the issues in JIRA makes it more user friendly for scrum masters who are managing multiple scrum teams in a program
- Automated dashboard creation and ability to create different charts makes it very easy for showing management rpeorting on different scrum teams progress in a sprint
- Sprint and version reports (out of the box) which provides burn down charts and which issues are lying in one state for more than a specific period of time helps scrum team to move forward and resolves impending issues
- Ability to link issues for dependency and flexibility to define SDLC life cycle for an issue on a board makes it very handy on any type of project

Cons

- No single view is available to see clearly how dependencies are moving forward
- There are times when single issue has to be given to multiple people like in pair programming one way is to create sub task but that is not an approach that was liked by scrum teams
- There macros / gadgets that comes with the JIRA product are very minimum they should add more gadgest for reporting purpose.
- Yes, there are different third party gadgets but sometimes those are not JIRA / atlassian recognized and for enterprise application and corporates using JIRA does not go ahead to deploy those third part gadgets on the server model.

Pros

The issue search or search filters are really helpful and easily we can save our own filters and share it with the team. This really helps us to manage different team's sprints and backlogs easily.

Cons

The new Active Sprint view limits or restricts users to understand the main story and its subtasks. It is difficult to navigate or track the original ticket in an Active sprint view. As an alternative to this, we navigate to Backlog view and from there we track the Active Sprint tickets. The Active Sprint view should provide option to enable or disable the view of sub-tasks for the tickets. I mean, more customization here would really help users to make their own choices.

Pros

Jira Software is a powerful project management tool that offers numerous benefits to teams and organizations. One of its key strengths is its flexibility and customization options. With Jira Software, users can create custom workflows, issue types, and fields, allowing them to tailor the tool to their specific needs and processes. This can lead to increased efficiency and productivity, as well as better project outcomes.Another major advantage of Jira Software is its robust reporting and analytics capabilities. The tool provides a wide range of built-in reports and dashboards, which can be customized to display the data and metrics that are most relevant to the team or project. This can help teams identify areas for improvement, track progress towards goals, and make data-driven decisions.Jira Software also supports Agile methodologies, making it an ideal tool for software development teams that follow Agile practices such as Scrum or Kanban. The tool includes features such as backlog management, sprint planning, and burndown charts, which can help Agile teams stay organized and focused on delivering value to customers.

Cons

it can be complex and difficult to use, particularly for teams that are not already familiar with Agile methodologies or project management best practices. This can lead to a steep learning curve and require significant investment in training and support.

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

I am a technical writer who used JIRA as my first introduction into working in a close-knit, agile programming environment. I really appreciated the clean design, multiple ways to accomplish tasks, and logical visual representations of concepts. Is something assigned to you? It has your face on it. We had several development teams working in tandem and JIRA allowed for each team to structure their sprints according to their own preferences (some had more traditional set up and others used kanban). As time went on we were able to add more projects to JIRA, after transitioning off of ClearQuest for our baseline fixes, and while there is certainly a learning curve getting established programmers who have used one system of tracking for 10+ years converted to using JIRA, most everyone was able to transition and feel comfortable within a few weeks. Speaking as a non-programmer, I found JIRA to be incredibly useful and easy. Tracking writing and editing projects through development didn't require any specific setup or features and it was all around a great tool.

Cons

While it was great that every project could be tracked from our one JIRA site for my relatively small (30ish people) development team, any time fields needed to be added for one specific team to track something for stories or bugs, it was there for everyone. This led to having rather cluttered add screens that meant for a good deal of scrolling. I know some of this was surely user error, but having a bit more control would be nice. Also, the search function occasionally would just... not work. At all. As adorable as the sad faced little magnifying glass was when this happened, it would be very frustrating to lose functionality without warning. Being browser-based always makes for risk and some days would just be constant checking of if JIRA was up again so untracked progress didn't fall through the cracks.

Pros

First of all, this product offered a free trial to experience the features first-hand without any strings attached. It was great to have the ability to go and play in a sandbox environment and carefully evaluate what it can and cannot do for me and how it can add value to my organization. Set up and gaining access was easy and quick. The different permissioning levels make sense to stay organized and maintain accurate information. Some of the features I liked the most was having a great UI for exploring and learning without much training. I was personally tasked with setting up a couple of projects and the respective boards for my teams and I was able to do that in a pretty self-serve way. The design is minimalistic and doesn't feel overwhelming, it is clean and navigable. Easily creating backlogs, sprints and administering those are also my favorite features because it makes it so easy to implement an Agile project management and software development culture. The categories of initiatives, epics, stories, tasks etc. align very well with the Agile methodologies in following the same hierarchy. I love being able to get a quick summary view of the tasks before diving deep into the details. Assigning owners, labeling, story points to track work effort needed, description fields, attachments, comments and seamless integrations with other products make it all the more user-friendly. Kanban Board views in Active Sprints tabs provides a clearly easy to understand view of progress.

Cons

Managing boards within each project is the first that comes to mind. Jira does not offer a standard naming convention for the projects and boards and this can cause some major confusion. I have hard coding this manually and training people to do the same to ensure consistency. If you attached Lucidchart diagrams or embed other important document within tasks or epics, they don't update in real-time or even with refresh which is frustrating. This runs the risk of people getting outdated information which can misinform their actions. The search functionality within Jira is also something that I like the least. It does not return optimal results or even close to optimal results. Sometimes it does not search for metadata and you have to remember the actual word you're searching for to track down a task. It returns an overwhelming amount of results and the filtering or sorting options available are confusing and hard to understand. Another limitation is that even though one project can have multiple boards within, it can only have the one same backlog of items which does not make sense to me. There also cannot be multiple sprints running across different boards and all of this makes me wonder what the actual difference between projects and boards are. Jira also lacks some automation in moving tasks to different statuses upon completion. The workflows are suboptimal and don't work as intended most times. The reporting capabilities within Jira are also quite weak in my opinion.