Jira

What do you like best about the product?

Jira has been a dependable tool for managing marketing projects, campaigns, and cross-functional collaboration. It keeps our work organized and offers solid visibility into task ownership and overall progress. That said, it can sometimes feel more tailored to engineering teams than to marketing users.

What do you dislike about the product?

It can feel overly complex for what should be simple marketing workflows. Reporting and dashboards also require some initial setup before they become truly useful. Overall, the interface can be overwhelming for new users, especially at the beginning.

What problems is the product solving and how is that benefiting you?

Jira helps us organize marketing projects, track campaign progress, and manage tasks across multiple team members. It improves visibility into priorities, keeps everyone aligned on deadlines, and reduces the need for manual follow-ups, resulting in better collaboration and more efficient campaign execution.

What do you like best about the product?

For using it for agile development and defect management.

What do you dislike about the product?

We also use Jira as a case management tool, but it comes with lead time and significant overhead when we try to use it specifically for HR case management.

What problems is the product solving and how is that benefiting you?

It helps us track mobile development work that spans multiple sprints, and it keeps track of functions and features. We also use it as a case management tool.

What do you like best about the product?

The strongest parts are:
Centralized task tracking
Having all work items—bugs, features, improvements, and support requests—in one place reduces confusion and makes it easy to find the latest status on anything. Instead of searching through emails or chat threads, I can quickly see what's assigned, what's in progress, and what's blocked.

Kanban and Scrum boards
The visual boards make it easy to understand team workload and project progress at a glance. For example, during a sprint, I can immediately see which tasks are stuck in review and which are ready for testing, helping the team address bottlenecks before they become delays.

Custom workflows
Being able to tailor workflows to match a team's process creates consistency. For instance, requiring code review and QA approval before a ticket can be marked complete helps ensure quality without relying on people to remember every step.

Powerful search and filtering
Jira's search capabilities save a lot of time. When investigating a recurring issue, I can quickly pull up all related bugs, see their history, and identify patterns that might otherwise be missed.

Dashboards and reporting
Dashboards provide visibility for both team members and stakeholders. Burndown charts, sprint reports, and custom dashboards make it easier to track progress, spot risks early, and communicate project status without manually compiling updates.

Integration with development tools
The ability to link code commits, pull requests, and deployments directly to Jira issues creates clear traceability. When a bug is reported, it's easy to see the associated code changes and determine whether a fix has already been released.

Automation
Simple automations—such as automatically assigning tickets, notifying reviewers, or moving issues between statuses—reduce repetitive administrative work and help keep projects moving without constant manual intervention.

What do you dislike about the product?

Jira (by Atlassian) is powerful, but it comes with a few well-known pain points—especially once you move beyond small or straightforward projects.

One issue is how quickly complexity can snowball. What begins as “just a board” can turn into layers of workflows, issue types, permissions, and filters. It’s easy to overconfigure Jira to the point where even basic changes start to feel risky.

There’s also the admin overhead. To keep Jira healthy in a larger organization, someone usually needs to actively manage schemes, permissions, automations, and project configurations. Without that ongoing ownership, things tend to drift into inconsistency and messiness.

For non-technical users, Jira often isn’t very intuitive. Even core concepts like epics vs. stories vs. tasks can be confusing, and for non-engineering teams it can feel like you’re learning the system itself rather than simply tracking work.

Performance and overall “heaviness” can become a problem in large instances. In bigger Jira setups—with lots of projects, custom fields, and plugins—it can get slow or cluttered, and searching, loading boards, or applying filters sometimes lags.

Another pain point is the tendency to rely on configuration instead of simplicity. Jira gives you a lot of power, but many teams end up building overly complex workflows when simpler tools or processes would work better. That flexibility can become a trap.

Finally, there’s some UI/UX friction. Small things—like creating issues, switching contexts, or navigating between projects—can take more clicks than necessary. It works, but it isn’t always smooth.

What problems is the product solving and how is that benefiting you?

We use Jira to manage software development projects, track bugs, plan sprints, and coordinate work across engineering, product, and QA teams. Before adopting Jira, it was difficult to maintain visibility into project status, prioritize work consistently, and ensure that issues weren't overlooked as the team and backlog grew.

Jira provides a centralized system for tracking all work items, from feature requests to production bugs. Its Scrum and Kanban boards make it easy to monitor progress, identify bottlenecks, and balance team workloads. We also use custom workflows and automation rules to standardize processes and reduce manual administrative tasks.

One of the biggest benefits is improved visibility and accountability. Team members can quickly see priorities, dependencies, and ownership, while managers and stakeholders have access to real-time reporting and dashboards. This has reduced time spent in status meetings and made sprint planning more efficient.

The integration with development tools also improves traceability by linking code changes, pull requests, and releases directly to work items. As a result, we've experienced better project organization, fewer missed tasks, faster issue resolution, and more predictable delivery timelines. For teams managing multiple projects and cross-functional collaboration, Jira provides a scalable way to keep work organized and aligned with business priorities.

What do you like best about the product?

I like how in Jira I can categorize work by type or epic, and it's easy to visualize with its minimalist design. I also like how I can drag a task, issue, or story into the Epic and move them through different phases. It helps keep our backlog organized and prioritized.

What do you dislike about the product?

Maybe its formatting, sometimes it looks a bit funny when I save the copy on each card. I have to spend time fixing the spacing and bullet points. The spacing and bullet points don't always save/look correct. Especially copy/pasting formatted text into the cards.

What problems is the product solving and how is that benefiting you?

I use Jira to create tickets for our team, keeping our backlog organized and prioritized. I like how we can categorize work by type/epic, and it's easy to visualize with a minimalist design. I can drag tasks into Epics and move them through different phases.

What do you like best about the product?

Many internal features like Tickets management, confluence and integrations with 3rd party apps for testing. Great UI and work fluently well even in 1000 of tickets.

What do you dislike about the product?

One aspect I dislike about Jira is that it can feel overly complex, especially for new users or smaller teams. The large number of configuration options, workflows, issue types, and permissions can make it difficult to navigate and maintain. It can also become cluttered if projects aren't well organized, making it harder to find relevant information quickly. However, these challenges are generally manageable with good project governance and standardized workflows, and the flexibility Jira provides often outweighs these drawbacks for larger engineering teams.

What problems is the product solving and how is that benefiting you?

Jira helps solve the challenges of planning, tracking, and managing software development work across teams. It provides a centralized place to manage backlogs, sprints, user stories, bugs, and tasks, while giving visibility into progress, priorities, and dependencies.

As a Lead Frontend Engineer, Jira benefits me by helping me:

* Plan and prioritize work effectively during sprint planning.
* Track the progress of features, bugs, and technical debt in one place.
* Collaborate efficiently with product managers, designers, QA, and backend engineers.
* Monitor sprint health using dashboards and reports such as burndown charts and velocity.
* Maintain traceability from requirements through development, testing, and release.
* Integrate with tools like GitHub, Bitbucket, and CI/CD pipelines to streamline the development workflow.

Overall, Jira improves team transparency, accountability, and delivery predictability, allowing us to focus more on building high-quality software and less on managing work manually.