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,888)
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.
The incumbent continues to be the incumbent for a reason
Comments: I learned to like Jira and although I am shown options quite often, they are mostly copies.
It is what everyone knows and learns how to use.Jira can handle multiple workflows, highly customizable for each team wich is highly appreciated by the different teams. It is not a one size fits all.
It keeps on adding new tools to the offer, if not always well-integrated, especially from an admin and billing pov.
Reasons for Switching to Jira: The other ones didn't math or justify the cost of change
Efficient and Flexible IT Project Management with Jira Features
Comments: My overall experience with Jira has been positive. The platform has improved our project tracking, bug resolution, and overall collaboration within the team.
I appreciate Jira's efficiency of project management capabilities. The flexibility it offers in creating and managing tasks, along with a customizable workflows for US and BUGS, ensures that our team can tailor the platform to our specific needs.
The interface might feel overwhelming at first view, and some features require a bit of exploration to fully understand. Additionally, the pricing can be a consideration for smaller teams or organizations with budget constraints.
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.
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
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
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.
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.
Jira, Streamlining Team Collaboration
Comments: Jira is considered as a robust and powerful project management tool that provides teams with the tools they need to collaborate and manage their tasks, issues, and projects effectively. The tool offers a wide range of features, such as task management, workflow configuration, collaboration, reporting and project tracking, alerts and notifications, access controls, calendar management, document management, and integrations with other tools.Jira's flexibility allows teams to customize their workflows and processes to match their specific requirements, and it provides a range of built-in templates to help teams get started quickly. The tool's collaboration features, such as commenting and notes, help teams to stay informed about the status of their work and provide feedback and share ideas.
- Task management: Jira offers a comprehensive system to create, assign, and track tasks, with built-in templates to simplify the process.- Workflow Configuration: Jira allows teams to customize their workflows to match their specific processes and requirements, with built-in templates to aid in setup.- Collaboration: Jira provides a range of commenting and notes features to enable easy communication and collaboration among team members.- Reporting and Project Tracking: Jira offers a variety of reporting and project tracking features, including real-time data, visualization options, and built-in reports to help teams track progress, identify trends and measure performance.- Alerts and Notifications: Jira provides real-time alerts and notifications to keep teams informed of important changes and updates to tasks and issues.- Access controls and Permissions: Jira offers role-based access controls to manage access and permissions for different users and groups.- Calendar Management: Jira has a calendar feature that enables teams to schedule and manage their tasks and projects.- Document Management: Jira provides a central location to store and manage documents, such as files and images.- Integration: Jira can be integrated with a wide range of tools and applications, Like Slack, Google Calendar, Google Drive, Trello, GitHub, Bitbucket, Microsoft Excel, Word and Outlook & Zendesk.
Jira is a powerful tool that provides a wide range of features to help teams collaborate and manage their tasks, issues, and projects effectively, but as it is a complex tool, it may require some time to set up and use. Also, the UI can be cluttered and confusing for some users, and the performance may be slow when working with large projects or many users. The mobile app may lack some features compared to the web version, and the reporting and analytics features can be limited. However, Jira offers many integrations, which can help teams to work more efficiently and effectively.
Reasons for Choosing Jira: - Advanced features: Jira offers a wide range of advanced features such as workflow customization, agile methodologies, reporting and analytics, and integration with other tools, which can be beneficial for teams that need more advanced functionality to manage their tasks, issues, and projects.- Scalability: Jira is designed to scale with the needs of organizations, and can handle large projects and teams with ease, which can be beneficial for organizations that are growing and need a more robust project management tool.- Ease of use: Jira is designed to be easy to use, with a user-friendly interface, built-in templates, and a wide range of resources and tutorials available online, which can be beneficial for teams that are new to project management or software development.- Cost: Jira is considered to be cost-effective solution for teams of all sizes, and the pricing plans are competitive compared to other project management and software development tools.- Integration: Jira offers a wide range of integrations with other tools and applications, which can help teams to work more efficiently and effectively by reducing the need to switch between different tools.
Reasons for Switching to Jira: Due to its advanced features such as workflow customization, agile methodologies, reporting and analytics, and integration with other tools. It is scalable and can handle large projects and teams with ease. It is easy to use with a user-friendly interface, built-in templates, and a wide range of resources and tutorials available online. Jira offers a wide range of integrations with other tools and applications, which can help teams to work more efficiently and effectively by reducing the need to switch between different tools. It offers advanced reporting and analytics features such as real-time data, visualization options, and built-in reports to help teams track progress, identify trends, and measure performance. Additionally, it provides support for Agile methodologies, collaboration features, customizable workflow, mobile app, and it is cost-effective. All these factors combined make Jira a powerful and versatile tool that can meet the needs of various teams and organizations.
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.
JIRA is essential for good software development but you NEED to invest in configuration
Comments: I love JIRA because I am an organizer and I spend the time getting it right. But you need that kind of commitment for the best experience.
The powerhouse controls that allow you to configure exactly the solution you need. JIRA is unmatched in customization. For controlling workflows, getting status updates and clearly understanding what's on your plate, JIRA is amazing.
The use of JIRA without properly configuring it. Without that commitment, JIRA can be offputting and seem like a heavy mess of a system. You need to remove what you don't use, need to set everything up for individuals and you need to educate your team about how they can use the system. It's so open that it can overwhelm people without management.
Reasons for Choosing Jira: JIRA is more structured and better at reporting.
Switched From: Bugzilla
Reasons for Switching to Jira: A comprehensive solution, including the use of Confluence for doc management.
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.
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!
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.
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.
JIRA - The monolith everyone uses
Comments: We use JIRA to plan monolithic projects across our organization and communicate with teams in multiple time zones and regions. We have a tier 1 tool plugin that allows our tier 1 support to escalate tickets for tier 2 and that is where we perform our work. I work indirectly with our JIRA administrator and project managers to support them while they support the JIRA platform for our organization. I have worked with JIRA in numerous organizations and while I've given it a mediocre score overall, it is a useful and irreplaceable tool overall.
JIRA is an industry standard tool, due to this it's very well known and a colloquial metaphor for "tickets" in and of itself. JIRA is able to handle monolithic projects and the many related projects with regard to them. JIRA is very good at allowing and automatically building self-referencing tickets within it's comments and ticket parts, if you put a ticket title into a ticket it will automatically reference the actual ticket with a link. It is also very good at adding to existing tickets with related tasks, sub-tasks, and prioritization. JIRA also is considered in almost every third party tool with a massive volume of software that offers "JIRA plugins" considering it's high stature with the IT community.
JIRA is "the tool" but it's not "a good tool" for every project and company size. JIRA is like other commercial grade products that just aren't designed for simple day to day use. While it opens up nicely and begins to make tons of sense in larger projects, larger organizations, and larger teams it often doesn't show the same beauty with simple projects and day to day ticket tracking. Additionally, the JQL language is ridiculous follows in the foot steps of many other proprietary languages that are only great for constant users of JIRA. While that's the implied scenario because as mentioned JIRA is "the tool" it's not always the case. When my day is split 20 ways, I have little time to sit down and do more than plug in a JIRA ticket number to get to the issue to investigate, review, get sign off on a fix, and apply. JIRA is also having what appears to be a lot of difficulties this year staying online with their new data center providers. I don't remember ever having these issues prior to their most recent move.
The "Ticket or No Ticket" Debate
Comments: It took time to get buy-in from the entire IT department to fully utilize JIRA. However, now that the whole department is all-in, JIRA has truly made our work effort much easier. We now have internal business partners who utilize JIRA to review work status, set priorities, and create new tickets when issues/upgrades present themselves. With an organization our size, I can't imagine not utilizing something like JIRA...not sure how we did it all in the past.
The best part about JIRA is the ability to keep track of all work being done via tickets. I love that JIRA works for all kinds of styles of work. We work within an Agile environment, with some teams using Scrum and other teams using Kanban. No matter how the team is structured, they utilize JIRA tickets. This is great because there is a single repository for all work being done and we can easily search for tickets across all the different teams. The use of Epics vs. Stories is very easy too. We can keep track of what tickets belong to which effort with ease and show the progress of work through the tickets. We can also easily maintain a backlog of tickets. If two separate people submit a similar ticket (or at least two tickets that reference the same work effort), we can combine those tickets easily so that we aren't feeling overwhelmed with more tickets than actual work.
The biggest debate among our team members is when it is necessary to create a ticket. JIRA has created a culture of needing to log every little thing, even if it takes just a moment to complete the work. Sometimes, it takes longer to create the ticket than to complete the task at hand. That tells me there is too much reliance on JIRA to report work completed. It causes some in management to show that their department is succeeding simply by the number of tickets completed. But the tickets don't tell the whole story, especially because there isn't a time component to those tickets being completed.
Great all-around tool for Agile project management and software development!
Comments: My overall experience with Jira has been great so far. There is a lot more to learn and Jira provides that opportunity to create the best experience for me and my colleagues. They do keep introducing new features and facilitate an active community to gather feedback and actually act on it. Jira has definitely added a lot of value in how we do project management and software development at my company. It has his flaws but it still works out to be the best tool for us to accomplish the purpose at hand this far. I'm sure it will only get better from me and we can get the utmost value from Jira in the long run.
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.
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.
Jira is a project management software
Jira is a task administration programming that is very mainstream among numerous organizations. With an extremely high score of 9.4/10 and client fulfillment at 99% it is as of now one of the best 3 best task administration arrangements looked into on our site. The primary spot in this class is held by Wrike which has an aggregate score of 9.8/10 and is the champ of our Best Project Management Software Award for 2017. You can experiment with Wrike for nothing here. You can likewise contrast Jira and Wrike and see which one is better for your organization. Jira is intended to enable clients to catch, dole out, and set needs to their work. It enables you to deal with the entire procedure of use improvement ensuring that everything is secured, from idea to dispatch. Its straightforward, natural interface empowers joint effort with partners and enables you to take care of business in a viable way. Jira tailors itself to fit to the necessities of the business and gives fantastic help to finish everything. The level of customization enables the product to properly fit distinctive business needs. This product can be utilized by an organization. I have designed JIRA to be utilized by distributing organization, by law office, and obviously, IT organizations. What's more, it was conceivable to make everybody content with what JIRA gives. Despite the fact that occasionally it was difficult to encourage individuals how to utilize it, following multi month or two they couldn't recollect how they lived without it.
Jira is an amazing programming, however with a lot of capacities comes a large group of devices and assignments to learn, especially for new clients. As of late JIRA refreshed its outline. My clients whine about new outline, I get insane when I can't discover things. Furthermore, JIRA wouldn't like to stop at that and is refreshing its plan further and further. I would truly incline toward that they glance through bugs that were raised on comunity entryway and accomplish something in regards to new highlights as opposed to doing configuration refreshes. It is imperative to realize that Jira gives us awesome help to the client, and their consideration is a need, however ordinarily they don't figure the issue. It is a component to survey in Atlassian. - The prologue to Jira's reality is required to be as mysterious as its interface and execution. Actually it is intricate to fabricate channels and move around in the application when the client is new. - You need to run a right download of the reports toward the finish of the month or toward the finish of the week, the reports are conveyed in spreadsheets, however with an introduction that fails to impress anyone, thusly, when setting the dates they ought to have pretty much days so you can play out the download effectively.
A project manager’s dream
Comments: A very strong tool for development projects, which covers so much more than just project management. Thanks to Jira, you can track issues over the whole development life cycle. Entire project layout is possible with infinite iterations, including planning and backlogs. The variety of collaboration tools involved (like comments) is unmatched by all other tools I’ve used. The project progress is easily tracked, plus you can track then across releases. Jira offers full reports on both progress and performance.
One of the best features I’ve found in Jira is the Workflow editor – I’ve never seen anything like it despite my extensive experience. Some people would say it’s not even that important, however, for growing businesses it’s something you can’t do without. Lots of task tracking is needed all at once, as you can never predict what necessities will arise in a growing company. Jira provides great help with all these issues. Sprints can be structured across multiple tandem-working teams, taking into account their wishes and preferences – either for traditional setups or for newer ones.
Honestly, one thing that was really off-putting for me was the impressively complex layout. The project list is simply huge, and you have to take some time to grasp the navigation and search features. Perhaps, in the next update the developer needs to add the possibility to tag or somehow categorize or classify projects more clearly to make them easily searchable. Otherwise, it takes a bit too much time. The dashboard is simple, but I don’t much like the visualization for reports. You also can’t assign tickets to several people at the same time. Only the person who created the ticket has the authorization to close it, which is quite bothersome. You can’t create columns or tables, and notes exist only for text input. I would also like to see a feature where you can generate turnaround time for ticket closure in an automatic way using reports. Plus if you have a bad Internet connection, there are issues with loading contents (sometimes the loading even stops altogether).