With 15+ years in the agile space, Jira offers teams the top tools and best practices to provide the right foundation for growth.
It’s ease of use to set up different help desks or ticket requests was fairly easy. Each help desk can be unique to the department it serves.
I dislike both how it's hard for me to use and how it's hard for others to use - I run into instances of people misunderstanding the software all the time, which creates mistakes and wasted time.
Filter reviews (13,865)
Complete Project management Solution
Comments: It's a great all in one agile tool. It's easy to use and very powerful. Jira has a lot of integrations.
I've been using Jira for over 12 years. The software has grown and improved over time. Jira remains a leading product in class.
The billing is a pain. Bitbucket is separated out and it's hard to manage the different accounts. The billing panel needs to be easier to use.
Alternatives Considered: ClickUp
Reasons for Choosing Jira: Azure Dev ops was quite expensive and the user management is painful
Switched From: Azure DevOps Services
Reasons for Switching to Jira: Jira is purpose built for Agile. Click up is one of those do everything tools.
Jira is great tool for agile teams
Comments: Overall, Jira has some great features for project leaders but this product can be difficult to transition to due the lack user research on Atlassian's part. The transition can be slow and tough but once the teams are trained up the tool, the tool can become invaluable to work with.
Jira helps team discover agile foundations with the guide of a scrum master or project leader. The sprints provide guardrails to teams take smaller chunks of work. Jira provides a centralized location to work in and can reduce the amount of communication gaps.
The greatest opportunity Jira has is that the user experience is rough in the fact that the product needs in-depth training to properly use it. For example, there aren't any youtube tutorials or best practices documents on why the end user would use label or a component. Most project leaders I know do not have a standardization why they use that and it causes confusion on project teams. The product isn't a plug and play, it is more that any user will need several lessons on simple actions such as creating a story, creating a Jira board, and creating Jira JQL. At the end of the day, there is a steep learning curve for this product and that increases the resistance for enterprise teams to go agile.
My views on Jira
Comments: overall it was a nice experience with Jira. Most of the teams have knowledge of how to use it is an advantage that saves some time in learning
It has the capacity to manage multiple projects seamlessly and can cater to larger teams. It also has large userbase and easy to get help from the community
Some features are not there and some are hard to use with the user interface being a little tricky
For all tickets, both internal and external, we use Jira
Comments: JIRA has powerful reporting features; for instance, you can quickly build dashboards to monitor the status of different bugs. It's easy to use and works well with other programs. Our software engineers have relied on JIRA for years, and they've never been happier with the software.
Bug tracking and task allocation in software development are two areas where JIRA shines. Because of its adaptable nature, it may be fine-tuned to meet the specific requirements of any given project.
There isn't anything to be critical of in JIRA. New users may find the process flow to be a bit challenging at first. The UI might use some modernization in terms of aesthetics.
Project Management is easier with Jira
Comments: For sprint planning, we utilize Jira. Jira's best feature is that when we've entered the necessary information the first time, the system will recommend it for us the next time.
Our on-site team is able to keep track of defects and prioritize fixes with ease thanks to JIRA's bug tracking and project task tracking features. Since I oversee the distribution of resources across several clients and projects that employ shared resources, Kanban boards allow me to keep track of how much time each activity takes on its own.
Mobile access is a bit challenging when it concerns browser-based usage. One of the most effective methods of dealing with this is to create a high-quality user experience apart from any mobile app.
More effective project management and monitoring
Comments: Quickly aligning a software delivery team's members around a common vision is made possible without overwhelming them with a complex platform.
I appreciate that it's straightforward to set up, can be customized to fit any team's needs, and integrates with a wide variety of apps (from chat rooms like Slack to customer relationship management systems like Salesforce). simple, simple, simple, with a variety of dashboards and views to accommodate any team's needs.
The configuration process is not my favorite, and it could prove to be rather difficult for my team. There's also room for improvement in the user interface (UI), as it's not always reliable and can be frustratingly slow at times.
Manage your workflow with Jira software
I've been using Jira Software for the past year, and it's proven to be a valuable addition to our workflow. I appreciate its versatility, which allows me to customize workflows and issue types to fit our team's specific needs, like setting up a Scrum board to improve project management.
I wish the user interface was more user-friendly and that it had more features like built-in timelines and collaboration tools.
Start Managing projects in minutes
Comments: It is great to work alone or with teams. It gives great visibility on projects. You can manage the things you are working on and let everyone else know about it if you want to. You can also have files, images, videos, and documents as references. Your final product can also be shared and have everything in the same place.
The easy interface. It takes minutes to understand and start using it.
For the moment, I haven't encounter with any dislike.
JIRA, best software for project management
- Many features - Easy to use - Best performance
- Price is high - Need more document - Need more plugin
Great system for managing client projects
The system is massively flexible and can fit into different workflows for different needs
With so many features I can be a little overwhelming to start but using the inbuilt templates helps you get started.
Reasons for Switching to Jira: The flexibility of the system to grow with our needs
Team Project Collaboration is easy with JIRA by atlassian
Comments: My JIRA by atlassian experience has been good. It makes our project management great.
1. As a member of a Scrum team, I use JIRA by atlassian everyday and it makes it easy to collaborate. 2. JIRA by atlassian makes team collaboration easy especially when we are working on a common project. 3. One more think I like about JIRA is that it makes tracking my team's work flow easy like ABC 4. JIRA by atlassian is affordable compared to competitors in the same industry.
The customer support is not very responsive. I wish they would improve their customer support services.
Alternatives Considered: Workzone
Reasons for Choosing Jira: StoriesonBoard is expensive compared to JIRA by atlassian.
Switched From: StoriesOnBoard
Reasons for Switching to Jira: JIRA by atlassian is cheaper and more reach with features.
Great for Backlogs and Organizing Software Releases - Bad For Agility
Comments: Great software, but I couldn't believe there was no native chat support for assisting with issues. Really Atlassian? Are you that proud of the UI? You shouldn't be... you probably bought Trello because enough people were having a hard time figuring out all of Jira's quirks. Trello is so much easier and faster to get up and running for projects, so that was a good buy. Take notes.
The backlog and features for managing the backlog with different methodologies such as Kanban, Scrum, or Kanban + Scrum hybrid are very flexible. Planning sprints, releasing sprints, and looking at history of what was done is very organized.
Cumbersome to setup. Workflows for issues and UI/UX for creating them is not easy to understand. Sure you can figure it out, but it will require a lot of facepalms. It's good for larger organizations with several cross-functional teams, but if you are a smaller organization stick with Trello and checklists for the cards if sub-tasks are needed. The sub-tasks in Jira are just plain awful to work with, and will end up wasting a lot of time for your team.
Go Agile with JIRA!
Comments: Jira is very easy to use from the user perspective, as well as operating it from the Admin perspective. Overall I personally suggest this product, although its price not being very welcoming, it's definitely worth the money! If you're a very large organization you definitely will want to try Jira.
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.
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.
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.
Jira, the eldest son of the Atlassian family
Comments: Very positive experience and without any bugs. this has always favored teamwork which has benefited from a time consuming point of view.
a complete and very user-friendly workflow management tool that allows you to optimize work times with a perfect management of all tasks, collaborators, project delivery times and more generally "who does what" on each single activity. Thanks to the easy connection with Trello it is possible to have a complete and easily accessible platform also from mobile for the management of team work. once discovered you will not be able to do without it because it has a free version available complete with all the features you need to manage even complex projects.
I have been using this software for several years and I have never encountered a problem either at a technical level or at the interface with the different businesses that I have managed. Implementations are always welcome so I look forward to testing some new features that they will release in the future for now everything works great.
Reasons for Switching to Jira: It is a complete and easy to use tool in a team, especially with creatives and developers. Sometimes I integrate it with the use of other software that may already be used in agencies or private individuals.
Comments: Hugely disappointing attitude. The money they were looking for after 3 months was quite reasonable but the attitude of the customer support agent and the extremly deceitful and dishonest way that they promote this plan was a huge turn-off.
Seems like a very good software, is very powerful and is reasonably easy to use.
We found it through our Trello account, after Atlassian took over Trello. We were using another service desk software but noticed that Jira Service Desk could offer all the features we needed, and all for free! Or so we thought! The plan we chose is for small teams (which we are) and is advertised (still to this date) as "Always free for 3 agents". "Free" is further highlighted at the top of the Plans & Pricing page and a large "$0" is displayed. Well, it took some time to get it set up and to import our tickets (this is not easy and we needed support which was quite difficult to get). Once we got set up, it took some time to learn about it (no phone support on free plan!) and we devoted many hours to this. And all was well for about 2-3 months......then we receive an email to say that payment is due! And that our account would be cancelled if we don't pay! What? We contacted Jira, only to be told that we are on a temporary free plan, like a free trial, and that payment is due after 3 months I believe it was. We explained about the "free" plan that we signed up to but the Jira support member just reiterated her point and was quote blunt and unhelpful. We went back to check out the "Plans and Pricing" table on the Atlassian website, thinking we obviously missed the small print. But we didn't!!! They were still brazenly advertising "$0" and "Always free for 3 agents" and there is no mention of a free trial , anywhere on this page at all!!
Alternatives Considered: Zoho Desk
Reasons for Choosing Jira: Price
Switched From: Zendesk Suite
Reasons for Switching to Jira: Price and the solid experience we had with Trello (although of course Trello was another company for most of this time and had only recently been acquired by Atlassian.
HelpDesk Dream System
Comments: Overall I really loved the platform and the easy of use and they offer a mobile solution which allows you to manange, support and assist using your mobile device which is important which you are on the go and have customers who diesire information or support.
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.
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.
Best Agile development software in my eyes
Comments: Basically using Jira as my go-to software for tracking and managing any project be it business enterprise level or personal level. I would recommend anyone reading to this review to go try it and without a doubt, certainly you wouldn't regret ur decision!
Quick and easy management and organization of my backlog tasks, the flexibility of setting up almost any integrations for bug tracking with ease, works flawlessly when used alongside other Atlassian products like Confluence. Best pricing options seen till date. Overall takes my agile workflow to the ultimate level with the amount of extensiblity that is second to none in my opinion!
At times there is some flakiness in the outcomes of the actions but generally not a lot worrisome. Also the availability, although can be improved using a private cloud probably, does suffer some occasional hiccups here and there. The bug tracking is comparatively the most improvable area i suppose. It is good don't get me wrong, but can be so much more better with just a few tweaks here and there that's all.
Reasons for Switching to Jira: None of them stand a chance to match to this all-in-all amazing product!
Great for time tracking and task management, but some functionality is overly complicated.
Comments: As a project coordinator, I use Jira daily in a project management aspect, matching our planned work to progress completed by our teams. I maintain an overhead view of in-flight tasks and projects, and compare this data to outside sources we use for resource management, capacity to contract, etc. My most frequently used elements are a custom KanBan board which shows all in-flight, assigned issues for the entire company; as well as Tempo time tracking software and the reports tool.
I love the KabBan task view, our company uses this every morning for a company-wide standup meeting. We have set up a customized board with cards that display budget/due date/time spent/etc. and it has been invaluable to us during COVID-19, as we are all working from home and need to stay connected. Jira's time logging via Tempo has some buggy elements, but has been absolutely crucial in maintaining a clear view of task progress and budget maintenance. The time logging tools are incredibly reliable and allow the perfect amount of editing control by both administrators and users.
It is a big pain not being able to assign more than one user to an issue at a time, especially when making Jira issues for meetings, as the purpose here is to provide an issue to log time against. It has also been difficult for our company to systematize and homogenize project structure, as there was such a large learning curve to Jira project setup, and we have a large number of open projects. The functionality between projects differs greatly, and I think a large part of this is due to complicated project setup and maintenance. While Jira is very developer-minded, and many of our developers like it, it seems a slightly less appropriate fit for our designers/strategists and project management team. I also lack the ability to export some reports I need, for example a clear Estimates versus Actuals report in CSV form.
Finest application for the Agile software lifecycle
Comments: I use JIRA in all the Agile software development for classification and bug tracking for every user with Dashboards. I am satisfied with the JIRA features but I think JIRA needs to provide more integration towards CICD tools so that user can get more idea about the bug tracking.
Easy to create Agile dashboards to track bugs in different development life cycle. We can also extract informations regarding the user specific tickets created and worked for any period of time. Also we can attache documents to gives an entire idea about the the bugs and time tracker in comment section provides how much time it takes to fix the bugs. In the software industry JIRA is one of the widely used Bug tracking platform. The idea of classification of tickets like EPIC,Task are very useful to identify the work load needed for that ticket.
Need exact date and time of the ticket creation and comments when the ticket gets older, right now it describes like the ticket is "created more two weeks ago". JIRA also needs to integration with CICD tools for more information regarding the bug tracking and fixing. JIRA should provide a dashboard for each user how much time he worked on a ticket to track the overall work time and also it will be very easy for the Administrator also.
Alternatives Considered: Redmine
Reasons for Choosing Jira: Redmine lack Agile development life cycle features like an effective dashborad , exact classification of tasks and the work time logging.
Switched From: Redmine
Reasons for Switching to Jira: JIRA provided more features for the Agile development Lifecycle that suited our work environments and continues to give more features everyday.
The software an engineering department can not live without
Comments: Jira cuppled with Agile processes have driven the velocity and overall engineering teams to new heights at the company. I don't see a world where once you are on it you are with it for better or worse.
First of all I want to say Jira is DOMINATING the market. There is little that Jira cannot do which makes it a no brainer of everything most startups and companies will use. I love that Jira for the most part is a one-stop-shop for Engineering teams, IT teams, Knowledgebase, ticketing systems. You don't really see issues with using Jira until you get bigger. The fact that I can link Jira tickets to my Git commits and add confluence documents to my tickets and google drive files ALL IN ONE is ourtagious and its something my company loves inside and out.
Just like every software out there you cannot be perfect in all ways. Because Jira is a one-stop-shop the biggest issues we have is customization of Jira. Not because Jira cant be customized, but only because it can be customized so much that we need set Jira admins whos sole job it is to manage Jira for the entire company because of the huge learning curve because it takes so much time how to figure out even the littest changes to make our lives easier. On top of that, a big issues I see if that as you grow in Jira it is a money pit at times to have it scale with the company. At this point, we are so vested in Jira we cannot get off of it. Adding SSO, and Confluence, and CI DI, and all the features that they promote arent dominating their fields, but its like "Well.... We are on Jira and they don't integrate well with other software so if we want the best features I guess we will have to use all their software"
Alternatives Considered: GitLab
Reasons for Switching to Jira: Like I said, Jira is leader in the market for Engineering teams, it makes the most sense. Jira is the best software for startup companies needing it.
Jira is the Best Project Management Software
THe best software for project management ever.
It's paid, but even for our size of projects, we still love to spend some money on it and enjoy the good project management.
Everything ! the software is very powerful, it has a lot of options and features: - Scrum, Agility and flexibility of changing flows. - Security setup for every type of users. - A lot of features ( no way to compare it with any other software i know ) - Very simple to use - Sprints support.. - High Availability. - Awesome Designs ( old and new ). And so many other things i love about JIRA
I wish the cost was a little more less for small sized companies.
Alternatives Considered: Trello
Reasons for Choosing Jira: Trello is very limited comparing it to Jira.
Switched From: Trello
Reasons for Switching to Jira: The amount of features and the ease of use. Finally, everything is great about JIRA.
Works great for Software Project Management, I wish the configurations were easier to set up.
Comments: We are overall very satisfied with the product as the user side of the things are very solid. The administration is quite complex and if you are doing it on your own, it will take a long time and a lot of hours reading their forums to get things right.
The task tracking and overall reporting are pretty solid. If configured properly, you will not miss on any updates and can proactively resolve blockers.
The configuration. They are very complicated and you cannot expect a new user to get it right and that's why there are dedicate people who set up this. We did it on our own and it took us a couple of months to get things right.
Alternatives Considered: Pivotal Tracker
Reasons for Choosing Jira: DeskPro was slow and confusing. It's the opposite - the admin interface is pretty solid while the user interface was a lot to wish for.
Switched From: Deskpro
Reasons for Switching to Jira: I have been using it for 6 years at different companies so it was the most comfortable choice to make.
The best tool for a product manager
Comments: My experience has been great with JIRA and I have setup the product in my last two organizations. In my current role, the entire company has moved all their projects to JIRA. Despite some pesky UI bugs here and there, JIRA does everything that I need and has become a critical piece of my day-to-day work. It's never easy to build a product for product people, but JIRA has found a way to do most of what I need. I only wish the business would invest a bit more effort into their support team, but since many companies are already using JIRA, the internet has become a great substitute.
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.
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.
Comments: We are able to use JIRA to create, collaborate, test and deploy promos and emails for my company. I am able to see conversations and other notes from people I don't normally interact with, which can be really helpful in understanding issues that arise or other notes that may have been left out of conversation elsewhere. It's a great tool for us.
I work for a large clothing retailer that often runs promotional coupons and sends out emails to customers. JIRA houses all of the collaboration for our company in creating and testing these promos and emails. What I like is that everyone, from the communications team to the Quality Assurance Team to the IT troubleshooting team can be in one place to resolve issues quickly. I love that there is the ability to tag other users and quickly get attention to issues that need a fast turnaround (emails and promos are often made within 48 hours from creation to launch). I also really like attaching 'sub-tasks' to a main project; This keeps organization a priority without having to search for every related task associated with a project. Related to this is the ability to attach documents right to any project/task for easy download. You can save searches and filters to your home page. For example, I have a filter for viewing only email projects, and another for promotional information. Once you get results, you can sort by title, date updated and a few other categories.
At first glance, the layout is a bit overwhelming. You have a giant list of projects, and the search doesn't always bring up what you are looking for. It takes a bit of time to learn how to navigate. I would probably like to see 'tags,' or additional ways to categorize a project so that you can search for it through a few more parameters. For my needs, this isn't too important because of the short lifespan of emails and promos. But I could see other applications needing something like that.
Best Option for SaaS Development Management
Comments: After a number of years working with various tools, Jira is seemingly the best option for managing software development.
I have used Jira at a number of SaaS companies over the past 6 years and have found it to be easy to use for the most part. It is highly customizable and easy to implement; we migrated our current process from Pivotal Tracker to Jira with relative ease. In comparison to other similar products I have used in the past, it exceeds the competition in flexibility, integration opportunities, ease of use and implementation, as well as configurability.
I find myself running into minor bug-type issues somewhat regularly; like being unable to imbed an image in an item description at creation and only being able to do so in the edit view. Also have experienced issues with multiple users editing the same item and saving over one another's changes. Only issues have been minor that we've learned to work around.