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,350)
Amazing for issue tracking and project management
Comments: Great so far
JIRA's UI is very user-friendly and hence, it's easier to set up and onboard people onto it.You can create different projects for your different departments and manage your issues/bugs/tasks. Every Ticket has highly extensive options to provide detailed information and these can be edited later with ease. Timeline feature is also very useful.
I love this tool. The only thing that can be improved is the preview and size limit of the files attached to tickets.
Jira for Project Management
Comments: It's easier with Jira to manage the kanban and scrum requirements at basic & intermediate level, the complex workfows really ease the process managable in Jira. The system in place which makes the process enforced helps team to track the work items properly and auditable at times.
Jira is an amazing project management tool that helps team quickly get started with the tool on features to track their daily tasks, backlogs, srpints, & reports. The ecosystem is so flexible that it allows integration with many tools and wide range APIs to get the necessary things done in minutes!
There are still improvements required from UI/UX perspective where the issue view page can be made lot better. The complex workflows with the validators would require some more options in place.
Reasons for Switching to Jira: It provides easier configuration for workflows achieving the granular reuirements to make the process.
I think is the interface is better than other apps in certain things
Sometimes is hard to use filters if you are new
Effective tool to manage projects and track work
Comments: This application makes tracking the development of a project a breeze, saving me time and making the progress of the project clear to everyone involved. When it comes to keeping tabs on the status of various projects, Jira is the application that excels.
The project's progress and any arising problems can be monitored via JIRA. The most useful feature is the ability to set limits on how far along a work can be tracked and then assign it to a certain individual. Here, we can keep tabs on how long each stage of a project takes, as well as any problems that arise along the way.
For a first-time user to make sense of the system's many options, some training is in order. Getting more and more intoll kid tickets may be more trouble than it's worth.
Jira for all software related project management
Comments: overall I am happy working with the JIRA and its an essential tool for our software development work
It's Super friendly UI/UXVery popular and familiarity among team members Features like epic that organizes multiple tasks, bugs etc under one category and easy to measure the progress
Search functionality can be improved, sometimes its very difficult to find the issues based on the keywords in the entire JIRA and some advance search features like use of some special characters , sort options, date range etc should be present
Alternatives Considered: Basecamp
Reasons for Switching to Jira: Familiarity within the team and past good experience working with it
Best Tool so Far
Comments: I worked as a Product owner in a Multi National company where we were cooperating 5 Product Owners together with other PM's and Developemnt Teams .Jira made it very easy to cooperate and sync tasks amongst ourselves and easily share tasks to developers kew where to stop and where to start.
Easy to use compared to other previous PMO software used in the past, great at team management.
Time it takes to Customize a board end to end
Alternatives Considered: monday.com
Reasons for Switching to Jira: Price was better for first , administration was also a big plus since we could easily add Propper privileges when a new developer joined the team or give stakeholders read access.
Proper Project Planning Ensured
The level of collaboration and ease of use make it the perfect tool for team use. Issues are managed easily and debugging becomes easy due to the issue tracking that it offers. It also integrates well with other tools and increases productivity overall.
It can be quite daunting to set up at the beginning. But I would say this is common to other tools as well.
Alternatives Considered: ClickUp
Reasons for Switching to Jira: We found it more versatile and aligned to our project.
Best Tool for Managing Scrum
It's easy to create boards with inbuilt functionality and the use of jql. It's also a user friendly experience.
There can be a lot of complexity in filtering per your needs.
JIRA is solid for software development
Comments: I like JIRA overall. It is a good way to manage a dev team and see what stage various tasks are in. It can become a burden if users don't engage with it or extra steps get added to all tasks when they are only need for certain tasks/ sprints.
I like how easy it is to start ticketing and managing a sprint. It can sometimes be hard to document everything you need done in one task with pictures and such, but it creates a good framework in general to work off of. Better for sprints than epics in my experience.
Sometimes when many users across many parts of a project start interacting you get silos of data. It also requires constant attention to stay accurate and onboard new users.
Alternatives Considered: Trello
Reasons for Switching to Jira: I choose JIRA over Trello because it was better for documentation, reporting and other tasks we needed besides task management.
Comments: Its been more than 2 years that my organization have adopted to Jira and I don't think we would even think of another better tool as Jira has everything for a project to perfectly run.
Best tool to Manage entire project and as a tester it enables easy tracking of defects or issues and ensure quick fix. Along with team efforts required in a project Jira makes sure individual efforts are noticed.
At times while using Jira, if suppose my task for the day was not updated or something mismatches then its the days status goes wasted.
Extremely capable project management platform, but almost too flexible
Comments: Overall, it's been a great experience - but that was largely because we understood our own limitations, and kept our customization of the platform to a minimum.
Jira offers great flexibility: it can be adapted to any custom workflow, and readily supports custom fields/attributes. Also has fantastic API support for external integrations.
Jira's flexibility is also its achilles' heal. It's relatively easy to create workflows that aren't intuitive, or worse, leave users in "dead end" states that require admin assistance. Further, their implementation of Agile tools is still a bit awkward (probably because they acquired a 3rd-party set of plugins, and didn't really make the corresponding fields native). Finally, Jira's pricing represents a slippery slope - you can get started relatively inexpensively, but adding on options here and there rapidly adds up, and can make alternatives more price-effective.
Reasons for Choosing Jira: High cost, facing even higher costs to make it really usable
Reasons for Switching to Jira: API integrations with other tools in our software development lifecycle
Great Collaboration Tool For Teams
Comments: Great way to collaborate with team members and outside vendors on ticketing and projects, with a lot of integration opportunities. Would highly recommend to users not currently using JIRA.
It is a feature packed program that helps teams collaborate using a ticketing system. Much easier way to work with team members to fix issues, deploy updates and collaborate. Using this system between employees, departments, consultants and others we have been able to streamline collaboration on projects. It also has a lot of integration, including with Slack, to expedite notifications.
There is definitely a learning curve with this project and it can be a little hard to get the hang of, but once you do, the UI of the program will make sense.
Alternatives Considered: Basecamp
Reasons for Choosing Jira: Switched content and development companies who use JIRA instead.
Switched From: Basecamp
Reasons for Switching to Jira: More features and integrations over Basecamp.
JIRA is necessary to my everyday organization
Comments: I use it every day to organize my workflow. Without it, I would be pretty lost.
Agile development on Jira is great. The ecosystem allows me to track my time, organize my issues into tasks and sub-tasks, track when things get done, create estimates, and organize complex projects into smaller and simpler pieces.
The support is pretty ignorant of their user-base on several issues and refuse to add new features that would benefit hundreds, if not thousands. It can be very tricky to migrate, update, or set up. Plugins can cost money and it can add up, though I haven't spent too much at all for the value I received.
Alternatives Considered: Trello
Reasons for Choosing Jira: My prior employer used Asana but I found JIRA to be a better solution for an Agile workflow.
Switched From: Asana
Reasons for Switching to Jira: Trello is a watered-down version of JIRA and doesn't feature all of the technical details that JIRA has.
It works, but...
Comments: Overall, JIRA can work. It seems to require knowing what you're doing - including understanding Agile theory, your team's preferences, and how deeply you want to use the myriad features. This is not necessarily a bad thing, of course. If you don't know how Agile works, maybe take a class and figure it out. That said, most of the people I've worked with don't have the 20+ years of process study that I have undertaken, so JIRA is configured very lightly or customized to a point where it becomes a hindrance. The UI could really stand some updates for consistency and - yes - some hand-holding for configuration.
JIRA certainly has a lot of features that should make Project Management easy. The mobile app is adequate, and the web site works well enough. There are a whole lot of places to enter data, which ends up being a bit of a downfall. When JIRA is set up well, it does support PM. When it is used as a vanilla Agile product, I think it falls behind other offerings.
JIRA has so many configuration points that it takes forever to get it working properly for your team. They have also been changing the UI a lot recently, which has obscured where some data is, which - predictably - has slowed down our use. If JIRA could get a more consistent UI, I feel it could be a much better product.
Reasons for Choosing Jira: I would not willingly move from Rally to JIRA. I believe cost was the determining factor. Were I to have made a choice, I would go either with Rally or Azure DevOps. They both seem more forgiving of poor process implementation.
Switched From: Rally Platform
Reasons for Switching to Jira: Again, I believe this was largely cost. I would rather use one of the other products.
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.
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.
Track your Work from Start to End of Software Life cycle
Comments: Jira helps in maintaining our Scrum, Kanban and Devops culture. Its burndown charts, reporting, ease of all the roles working from product owner to dev all can be on on platform and in sync. Backlog can be easily managed and working hours are easily logged on same.
Its interface which gives a better look for team, whether defects are resolved or we can implement shift left strategy with charts provided. Sprints are easily executed from start to end and also Kanban is implemented with push and pull. SAFE can easily be implemented using this tool. It has good work log management and assigning task, where you can create sub task. Epic, theme, Task, SubTask Milestone can be created and tracked easily.
Documentation part is only maintained when everyone follows standard method of maintaining updated comments, in Sprints the scrum master has to remind for comments always. Chat History can not be added to the Jira, its only through conversation things can be tracked. Naming conventions like tagging is not shown for issue or defect to find and link to past issues
Reasons for Switching to Jira: Cost managementDrive innovationDrive revenue growthEnhance decision makingImprove compliance & risk managementImprove business process outcomesImprove customer relations/service
Highly flexible Agile project management tool but a little complicated to use.
Comments: I love using Jira as I can configure it as per my project's needs and I highly recommend this tool if your team is following 'Agile Development' process.
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.
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.
Excellent Project Management Tool - JIRA
Comments: - The overall experience with Jira is excellent as it helps in project management, deliverability tracking, time tracking and Jira can be integrated to other external applications like Copado which is used as CI/CD tool for Salesforce deployments
- Jira has the most critical features that every small to enterprise companies use to manage project management, application development, time tracking, workflow automation for various business use-cases, integrations with external applications like Copado (CI/CD) tool for Salesforce - Jira has very important usage in our company. All the teams uses Jira to manage all the deliverables and for tracking project management, feature releases, etc.
- The pricing of jira can be cheaper when compared to other alternate solutions available in the market - The support of Jira can be more available in all times to resolve critical issues - The UI can be more customized to better fit every customer needs without lot of overhead time
Reasons for Switching to Jira: - The pricing for Jira was good when compared to other products. - The customizations that Jira provides OOB was a huge plus for us to make the decision
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.
JIRA is a Great Tool - for the Right Teams
The best part about JIRA is how visual the UI is. It is incredibly easy to track down and track through different tasks and sprints without having the hassle of digging through a 90s-style ticket system. My other absolute favorite thing about JIRA is the simple ability to tag individual users basically anywhere. This saves an incredible amount of time due to the way in which notifications are handled in and outside of the system. Collaboration is beyond easy with JIRA.
Many of the most important features are being deprecated over time, and the customer service component of the software seems ineffective at best. Some of the best features have been removed and the highest priorities on their roadmap aren't those that would severely increase users' quality of life. I think this is part of a growing process that the company is going through, but it does cause some heartache on the regular to think that our business desires aren't being met - even through months of users requesting the simplest of features.
Reasons for Switching to Jira: JIRA had a much more robust interface than the other options we were looking into, and overall it was the visual aspects of JIRA that won out over the others.
Good features let down by a difficult hard to use UX
Comments: Integrates well with other tools including slack and visual studio online
We moved to JIRA from Visual Studio online because it supported Kanban better than Visual Studio Online at the time. On the plus side, it integrates brilliantly with Slack our team communication tool of choice. You can tag stories, create reports and link to tasks easily and very efficiently with the tags displaying in Slack conversations as JIRA links. Working with Visual Studio Git we tag all of our stories with the JIRA story numbers and they link together very efficiently. Confluence is included which is a Sharepoint equivalent. This allows you to create knowledge bases of information about your projects which you can use to document your product. You can easily embed reports into this using tags or the query tools. There are a great set of features and this tool integrates well with other systems
The UX changes on a fairly frequent basis and from experience not in a good way. It is still quite difficult after a year of using it to remember where things are because the controls are not as intuitive as they should be. There are a number of bugs with how the UI displays (particularly in swimlane kanban mode) and although it has fault reporting options, you don't feel that any changes you suggest or bugs you report are used. Confluence often feels like a poor persons version of sharepoint (which is not a recommendation) as it feels clunky creating pages, sections or defining navigation. The query tools are a bit like sql and partially fill in with suggestions but can be fiddly for the BA to create. This is a tool I would really like to recommend given how trendy it is but sadly after a year using I can't because whilst it's features are excellent it lacks ease of use.
Boost Your Team's Productivity with Jira.
Comments: In my experience, Jira Software is a powerful tool that can be a great asset to teams and organizations, particularly those following Agile methodologies. However, it can also be quite complex and overwhelming, especially for teams that are not already familiar with project management best practices. The tool's customization options and reporting capabilities are impressive, but they require significant investment in training and support to use effectively. Additionally, the tool's cost can be a concern, particularly for small or budget-constrained teams. Overall, while Jira Software has its benefits and drawbacks, it can be a valuable tool for teams that are willing to invest the time and resources needed to master it
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.
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.
In teams, jIRA is used to organize and automate collaboration.
Comments: If you have various add-ons, you can clearly see what is currently being done or worked on, have complete documentation of what has happened, and evaluate the time spent on various tasks. It also helps with error and task communication to other departments within the company. All of this can be compiled into various boards through various searches, allowing everyone to get their own take on the lists. JIRA organizes sales processes by determining who is in charge of which tasks, who has completed which tasks, what the relevant ToDos were, and how the results appear. How much effort goes into a sales process? Data analysis options for improving sales processes and resource planning.
JIRA is a highly complex and dynamic system that can be used to map all, even the most complex, tasks in projects in teams without the use of programming. As a result, all task-related processes can be created and tracked at the granular level. Workflow functions, as well as the concept of roles and rights, help with task management and ensure that the process runs smoothly. Jira can be integrated with any team tool, making it your primary source of information. The advantage stems from the documentation produced, which is primarily used for task distribution, management, and tracking. Time can be tracked and accounted for, as can projects. Everyone keeps a time log and records their questions, answers, workarounds, and other details.
Sometimes it is difficult to see the full complexity of a solution, which is all possible. Furthermore, because the results are frequently irrelevant, an optimized search would be advantageous. It took a lot of AddOns to make it "round." Costs should not be overlooked. My inbox is overflowing with emails.
Indispensable application...but setup is not for the non-tech savvy
Comments: When our internal IT Help Desk went down, we were in a bind. We needed something that we could get up and running with very little trouble and start getting help tickets going again. Despite there being a negative view of JIRA due to previous setup by non-technical users (who deemed it too complex); when the Help Desk was designed and implemented by the IT Team, there was very little talk of complication and more talk of how much better things were than the previous Help Desk. We did integrations with third-party collaboration tools and generated workflows and custom forms that made JIRA one of the best additions to our IT toolkit!
I love the quick and easy setup of JIRA spaces and it's integration with other Atlassian products. There are also a lot of third-party integrations to help fill-in the gaps.
JIRA is a beast. Plain and simple. Actually that's just it...it's not plain and simple. You have to have a good grasp of what you want from it to make sure you get what you really need. It is not friendly for the non-technical user looking to create a workspace.
Switched From: Microsoft SharePoint