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,244)
Filter reviews (13,244)
Easy and Comfortable
It is user-friendly, has cleverly thought out custom filters, has the ability to send emails, has a discussion about findings, we work with the scrum work method. That's why it's appropriate. The reports are very detailed. Job tracking and assignment is quite simple.
So far, I haven't come across a feature that I don't like. Me and my team are very satisfied.
Must have tool for every project management
Comments: Jira can help businesses improve their project management processes and workflows, streamline collaboration and communication between teams, and track progress and performance more effectively. With Jira, teams can manage their tasks, projects, and issues in a centralized location, which can help improve visibility and transparency across the organization.Jira can also help businesses improve their agility and responsiveness by enabling them to quickly adapt to changing priorities and requirements. Teams can use Jira's customizable workflows to automate their processes and ensure that everyone is following the same standards and best practices.Overall, Jira can help businesses solve various project management and collaboration challenges, improve their productivity and efficiency, and achieve their goals more effectively.
One of its strengths is its flexibility and customization. Jira allows teams to create and track issues, assign tasks, set priorities, and monitor progress through various workflows and dashboards.Another advantage of Jira is its integration with other tools and platforms. Jira can integrate with tools like GitHub, Bitbucket, Confluence, and many others, which makes it easier for teams to manage their projects and collaborate seamlessly.
One of the main criticisms of Jira is its complexity. Jira has many features and customization options, which can be overwhelming for new users. It can take some time to learn how to use Jira effectively and configure it to suit your team's needs.Another potential challenge with Jira is its pricing. While Jira offers a free version for small teams, its pricing can be relatively high for larger organizations or teams with more complex needs. Some users may find it difficult to justify the cost of Jira compared to other project management tools.
Alternatives Considered: Azure DevOps Services
Reasons for Switching to Jira: Because of flexibility and customization options. And also integration with bitbucket
The most used agile tool on the market
Comments: I have mixed feelings about Jira. I used it on a daily basis for years so it's hard to think about using something else. In the other hand, I wish I had something better to use.
It's the "standard", everybody knows it, everybody uses it. Every company I've worked for uses Jira, so there you go...
Support is far from good and they miss some simple, key features, for no reason. One good example is the fact you cannot add a simple checklist to a task (unless you pay for an expensive add-on that over complicates a very simple thing).
The user interface of JIRA is often praised for its user-friendliness and intuitiveness, rightfully
Comments: JIRA is a highly regarded and intuitive application within the Atlassian suite of software development tools. Users have praised its seamless integration with other Atlassian software, making it a comprehensive and cohesive solution for software development teams. The functionalities offered by JIRA are extensive and cater to various aspects of project management, issue tracking, and collaboration.
The user interface of JIRA is often praised for its user-friendliness and intuitiveness, making it easy for both technical and non-technical users to navigate and utilize its features effectively. Furthermore, JIRA offers extensive customization options, allowing users to tailor the tool to their specific needs and preferences.
Setting up the workflow and advance reporting features is complex. However, it is worth the time. If documentation and tutorials get better, it would be great. The application provides advanced reporting and analytics capabilities, empowering teams to gain insights into their project metrics, track performance, and make data-driven decisions. JIRA also facilitates seamless collaboration among team members, with features like comment threads, activity streams, and notifications, ensuring everyone stays informed and engaged.
Alternatives Considered: VersionOne
Reasons for Switching to Jira: With JIRA, teams can easily create and track tasks, issues, and projects, allowing for efficient project planning and progress monitoring. Its robust ticketing system enables effective issue management, ensuring that nothing falls through the cracks. Additionally, JIRA offers a wide range of customizable workflows, allowing teams to adapt the tool to their specific processes and methodologies.
One and only Jira
Comments: Jira's customizability and flexibility make it a unique and highly regarded tool for project management and collaboration.
Jira's agile boards allow teams to plan and manage their work using agile methodologies like Scrum and Kanban. These boards can be customized to match the team's specific requirements and provide valuable insights into project progress.
when working with large datasets or complex workflows, it can result in slow load times, crashes, or other issues that impact productivity.
Alternatives Considered: Asana
Reasons for Switching to Jira: Jira is highly customizable, allowing users to create custom workflows, fields, and issue types. Asana is less customizable, with fewer options for customizing
Keeping projects on track
There's multiple ways to manage projects, each with benefits, but being able to create sprints of tasks, and view them in a kanban board to brilliant. Syncing tasks with BitBucket and commits is also a great feature that creates accountability within a team.
JIRA does have a bit of a learning curve, especially if integrated within the other Atlassian products.
JIRA: Streamline Your Team's Workflow: A Comprehensive Review
Comments: Overall, JIRA's source control integration is a potent tool that can improve team communication and allow them to better manage their code modifications. If you are using JIRA to develop software, it is worthwhile to look into the source control integration choices and set up the integration that is most effective for your team.
Customizable workflows: Jira enables teams to design processes that are tailored to their particular development process. Therefore, regardless of whether they employ Agile, Scrum, Kanban, or other approaches, teams may quickly modify Jira to suit their needs.Integration with other tools: Jira has a large number of other tool integrations, including GitHub, Bitbucket, and Jenkins. Because of this, teams can easily keep all of their development tools in one location and track all of their work using a single system.Jira is a platform that enables teams to work together in real-time on issues and projects.configurable dashboardsAnalytics and report generation
JIRA is quite adaptable, however, some users have complained that it takes a lot of time and effort to do so. Creating reports, configuring custom fields, and setting up processes can be challenging and need a lot of learning by doing. When working with large projects or convoluted workflows, JIRA occasionally exhibits sluggishness and imprecision. The cost of JIRA is high, and its price structure is not always clear.
Indispensable within my team , as far as project management is concerned.
Comments: Jira plays a critical role in project management within my organization by improving the efficiency of project workflow management. With the ability to share essential project updates and information in real-time, Jira helps prevent duplication of efforts within my project team and eliminates communication overlap, leading to smoother team collaboration.
I find the drag and drop workflow automation builder on Jira incredibly user-friendly and customizable. By employing the simple "when, if, then" logic, I can easily automate and tailor workflows to meet the specific needs of our team projects. This feature has proven especially useful when setting up customized triggers within Jira for automating particular aspects of our projects.
Jira can be a challenging project management tool for beginners due to its steep learning curve. Without prior experience using Jira, new members to my team have experienced growing pains that lasted several weeks and months.
Jira customizes workflows flawlessly
Comments: Before deciding to use Jira, we evaluate all our needs to be able to manage and review our team, reviewing the project to determine if this is the right tool for you. Jira helped us provide our team with the necessary training to properly use and get the most out of the tool.
Jira is highly customizable and adaptable to the needs of each team. Users can customize workflows, fields and issue types, and create their own reports and dashboards. Jira offers a wide range of integrations with other tools and applications, such as Slack, GitHub, Bitbucket, Confluence, among others. We were also able to use Jira to manage our projects, not just software development projects.
Jira can be complex and it takes time for new users to get familiar with all the features and settings available. The license we purchased is an expensive tool, especially if you want to use the premium version. Sometimes its user interface is not very intuitive and may require a bit of learning to use it correctly.
Manage you process with Jira
Comments: Its very good application for manage project and set up time lines i'm using it for couple of years once you start working with it it becomes part of your job.
Application is richer in features and the functionalities. It provides more flexibility when working on it we can manage several projects at once by allocating peoples to those projects. Application provides better details about the projects via charts. we can create custom filters and custom charts as we wish. Most of the people use jira for manage Agile methodology but we can use it for Kanban also.
Application is complicated at the first sight but it gets familiar once start working.
Best and most true to tradition agile project/product management tool around
Comments: I have a (probably unhealthy) love for Jira and would need a lot of convincing to switch. It's interface is genuinely enjoyable to use and it aligns perfectly with agile product management methodologies, natively and in conjunction with its plethora of add-ons.
Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.
The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!
Alternatives Considered: Trello, monday.com and Asana
Reasons for Choosing Jira: Basecamp was rudimentary and unable to effectively visualise our cross-company/cross-team workload.
Switched From: Basecamp
Reasons for Switching to Jira: Jira was the most aligned with our internal development workflows and flexible enough to work for both technical and non-technical users.
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.
Alternatives Considered: Bugzilla and Trello
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.
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.
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.
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.
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.
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.
Flexible but not at all fun
Comments: Originally we wanted Jira to be the place for Product and Development. But we soon realised that we needed a separate app for the product team instead. So now the product team work outside Jira and only when it's ready for Development will a ticket get created and planned in the backlog ready for a sprint. Jira helps the Product Manager to know the status of features, bugs and tasks and allows the development team to ask questions relating to the ticket in the comment section. That way there is full visibility of the discussions for future reference.
The biggest strength that Jira has to offer is how customisable the app is. We're forever fine tuning how how development flows are setup and I've never run into an issue where what we wanted to achieve could not be possible. The workflow editor is pretty straight forward once you figure out how to map these to specific projects and features. It also has a mammoth number of apps that can integrate with it, which can greatly help simplify your organisations stack. We use a bunch of apps that connect to Jira such as Slack and Git. The mobile app is pretty good and more simple to use. There's also a new iOS app that you can run on a mac that seems to be a slightly faster and more user friendly version. However, I haven't quite worked out how to tailor the notifications. The search is very powerful!
It is very slow to load pages and jump between stories. When using this on a daily basis it really gets annoying. When we need to change a setting it's hard to work out where to go. I have to say I've never seen another app quite like Jira which has so many different places to go to in order to change very similar settings. If someone accidentally creates a ticket with the wrong type the only way to change it is to Move the ticket. And I can't seem to change the status of the ticket at the same time. So often an Open bug ticket becomes an Open feature ticket, which really should still be in Draft.
Alternatives Considered: Trello
Reasons for Choosing Jira: We hired a new Head of Development who encouraged us to make the switch as Jira had better reporting/time tracking features.
Switched From: Pivotal Tracker
Reasons for Switching to Jira: Although it was more simple to use it didn't have the time tracking and reporting features we needed.
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.
Alternatives Considered: Pivotal Tracker, Breeze, Asana and Rally Platform
Reasons for Choosing Jira: High cost, facing even higher costs to make it really usable
Switched From: VersionOne
Reasons for Switching to Jira: API integrations with other tools in our software development lifecycle
Review for Jira as a developer
Comments: We moved our IT department to start using Jira for the teams that work in development. We have not yet moved our Helpdesk or "system uptime" teams over since we are still looking at what product works best. So with the smaller team, I believe it has helped in keeping our tickets in order. It is simple to see what is currently being worked on in each project. We do not have the highest plan so we do not have all features, but I think our current feature set is large with room to evolve.
Jira is excellent at keeping track of our issues and linking between them on a kanban board. It was our introduction to a Kanban system of tickets. There are also many features we see ourselves using that we are on the verge of delving into, allowing us to focus on the tickets now but expand in the near future. I like that tickets are easily linked to each other. Our previous system made it difficult to know which tickets were related, while Jira has several options for relating tickets (related to, duplicates, blocked / blocks/ etc)
I think the price can get high depending on how big your team is. We were just over the free limit which becomes a large cost, especially once you include subscriptions to confluence etc. I think the load times and UI can get buggy at times, there are multiple times a day I have to click through menus several times for it to register. This is by far the most frustrating thing, especially when you have many tickets on a page. One issue we had was that our current ticket system allows us to CC users onto tickets so they (+ anyone else we add) can get an update. This was not possible through regular Jira, however something similar could be done with effort on the Jira Service Management side.
I enjoy Jira software but there are few things that can be improved in my opinion.
Comments: My overall experience with Jira is good and I do not plan to switch to other tool right now.
I like that I can really easily navigate between the projects because I am in multiple projects at once. I really like the possiblity to customize a lot of things, mostly the kanban board lanes and tickets details. I love linking feature, I find it really useful and I use it a lot. What is very important to me is also the Tempo application and I like how it's integrated in Jira, so I can really easily log my time into proper tickets. In our company we also use the Bitbucket and Confluence and I really enjoy that I can easily create feature branches, commits or pull requests from Jira itself. I also like the report tools to control my overall work.
I have a lot of diffuculties with Tempo application search issues feature. Since I am participating in a lot of different projects it is really hard to search proper ticket, neither using ticket code nor ticket name is not functioning good enough. Sometimes I feel also overwhelmed with the amount of features which I don't use at all and I am getting lost in the user interface.
JIRA Should Be Called the *Anti* Project Management Solution!
Comments: Our decision to transition our project management systems fully to JIRA is one of the biggest regrets I have made for our company. In addition to the cons notes above, things that should be core features are missing or available as a 3rd party plugin, for extra $$. What's worse is that Atlassian has a plugin system with half of the plugins only available for the server version and then they don't build features that should exist in the core product because they are available elsewhere... as long as you use the server version. Run AWAY from this JIRA as fast as you can!!
If you are willing to do the work, the advanced search is useful and the user experience isn't bad except that to eliminate done tickets you have to deselect all then re-select every option except those of a done type.
Advanced search is the only useful way to reliably get information out, making getting even the smallest view of your data onerous. The core advantage of the tool - it's lack of structure - make it difficult to complete even the simplest of tasks without a ridiculous amount of effort. It's biggest failing is that everything is too flat by default. For example, I am working on a project now and the team has made duplicate tickets because the original tickets are too hard to find and are just dumped on the screen... we have sometimes used epics/stories/sub-tasks with sprints but these are truly inadequate... in today's time why should someone have to spend 20-30 hours a week grooming the backlog and writing searches when if the tool was any good it should (!!) be able generate these views automatically. We are now investigating other solutions like Wrike (absolutely no affiliation, not even sure we will switch to it) and in 10 minutes of testing we were getting views that we have been struggling to get out of JIRA for over a year. Also, you can't do something obvious like make a reminder in the future for a ticket, so you either get flooded with reminders for just about everything or you have to go outside the product to remind you to do something in JIRA. Seriously!?!
A very powerful task tracking system
Comments: JIRA is easy to use and great for managing work tasks on a project, however customization options are often only available to admins.
Our company uses JIRA to manage work tasks. It has all the important features for assigning work to team members, tracking how long each task takes, notifications, capturing comments and hours worked. The tools allows for the flexibility to create your own JIRA ticket types or categories, with any kind of number of input fields. Data fields may be dropdown boxes, tags, values, or free text. Fields inherently have the ability to recognize hyperlinks and add those in once you type out a link, and it also recognizes JIRA links, such that if you enter a JIRA ID tag, it automatically creates a hyperlink to that JIRA entry. JIRA supports Agile development schemes and tickets could be easily tracked through a JIRA Dashboard. JIRA filters are also easy to use. You may use the basic query that provides you with simple dropdown fields for common elements, or you can create more advanced queries using JQL.
Being a JIRA user can be limiting as you only have the ability to enter data for the fields that are currently configured. You have to go through IT or the admins for any form of customization such as adding/removing/hiding fields, setting what kind of text format is in each field (e.g. plain text vs rich text) and modifying which fields are required vs optional. When you have rich text formatting, sometimes it can be frustrating getting the text to show up the way you want. The workaround for this would be to use the Text tab instead of the Visual tab so that you can modify the formatting tags.
Effective Project Management with Jira: A Review
Comments: Jira is widely known as a robust and flexible tool for software development project management. It offers a variety of features such as calendar management, Agile boards, customizable workflows, and built-in reports and dashboards that make it an effective tool for managing and tracking tasks, issues, and events. It allows teams to organize, plan, and collaborate on software development projects. Additionally, Jira's flexibility allows teams to customize their workflow to fit their specific needs, making it a powerful and efficient tool for managing software development projects. However, some users may find Jira complex to use and have a steep learning curve, also its pricing structure can be confusing and expensive for some small teams or startup companies.
Jira is widely known as an effective tool for project management. It provides a number of features such as calendar management, Agile boards, customizable workflows, and built-in reports and dashboards that makes it an effective tool for managing and tracking tasks, issues and events. Also, it allows teams to organize, plan, and collaborate on software development projects. Jira's flexibility allows teams to customize their workflow to fit their specific needs, making it a powerful and efficient tool for managing software development projects.
Jira can be complex for some users and have a steep learning curve. Some users find that it can be difficult to get started with the software, especially if they are not familiar with agile methodologies or project management. Additionally, Jira's pricing structure can be confusing and expensive for some small teams or startup companies. Some users also report that the software can be slow to load or slow to respond at times, which can be frustrating.
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.