What do you like best about the product?

Its strong issue tracking, workflow management, and the ability to organize tasks clearly across projects.

What do you dislike about the product?

The interface can sometimes feel complex, and initial setup or customization can take time.

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

Jira helps us track tasks, manage projects, and monitor progress in a structured way. It improves visibility, accountability, and collaboration within the team.

What do you like best about the product?

It helps us track issues reported by customers, set priorities, take action on them, and revisit them later for analysis. It also supports dashboard creation using JQL, which is very beneficial for viewing performance.

What do you dislike about the product?

If there were more dashboard widget creation options, it would be really great.

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

It helps me record and track issues reported by customers. It also makes it easier to coordinate with internal teams and get real-time updates. The dashboard visualizations help me understand where we stand on resolution SLAs and other key metrics.

What do you like best about the product?

I like most about Jira is how effectively it supports the QA process. As a manual tester, it helps me log and track bugs clearly, attach evidence, and follow their status until closure. The workflow and boards make it easy to coordinate with developers and keep testing tasks organised throughout the sprint

What do you dislike about the product?

One thing I dislike about Jira is that it can sometimes feel slow and a bit complex, especially when there are too many custom fields or workflows. Also, searching for specific issues or filters is not always very intuitive.

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

Jira helps our team track bugs, manage testing tasks, and keep clear visibility of issue status. It improves coordination between QA and developers and reduces confusion during the development cycle.
It also reduces time for manager to look up the things.

What do you like best about the product?

The thing which I would appreciate about Jira is that how amazingly it keeps organised everything in one place. It is really helpful while we are working with a team like to have tasks, bugs and feature requests all can be tracked in a single system instead of scattered across emails and chats. It has another part as well for like, it’s flexibility, I am able to customise workflows, create different boards and can adjust it based on how your team actually works rather then forcing them into a rigid process. Overall, Jira is an amazing and reliable tool for project management.

What do you dislike about the product?

It has many Configurations, settings and features so new user can take some time to explore it.

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

Basically it has given me the solution of overcoming the problem related to managing tasks and tracking progress when multiple people are working on the same project. Earlier my tasks, bugs and feature requests were easily getting lost in emails and chats. But when I started working on Jira, everything organised in one place and that makes it much easier to keep a track on what needs to be done and who is responsible for it. Jira has made my work much simpler and made the project management more structured and efficient.

What do you like best about the product?

I like the overall UX and the boards in Jira because everything feels clean and easy to understand and track. The layout is great because it shows information without needing to click too much, and moving tasks around is easy. I also appreciate that taking approvals from various teams is straightforward.

What do you dislike about the product?

I don't like its integration with other platforms like Teams. It would be much easier if I can provide the approvals or signoffs from the teams instead of having to open the link and type it in manually for every team.

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

Jira solves the issue of limited features in Excel and Smartsheets by providing a comprehensive tool for tracking backlogs, logging bugs, and managing releases efficiently.

What do you like best about the product?

I like that Jira has all the functionalities you expect from a ticket manager. The ability to define automated flows and custom fields is very nice. The API is quite comprehensive. Automated flows are useful for otherwise manual and repetitive tasks, like automatically propagating custom field values from parent to child. Custom fields are nice for segmenting data using proprietary values such as application and department. The API is nice for integrating with CLIs, extracting data manually for other workflows, or integrating with other platforms.

What do you dislike about the product?

I have always found that the UI was a bit all over the place and fairly 'sluggish' to use. Settings are all over the place as well and it's sometimes quite cumbersome to change the configuration of issues (e.g., association of fields with issue types and screens).

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

Jira helps me manage work in progress and backlog, and allows task assignment in Kanban mode. Automated flows save me from manual tasks, custom fields help segment data, and the comprehensive API integrates with other platforms for seamless workflows.

What do you like best about the product?

It provides an easy way to assign work tickets to developers and be able to track status. I also like the fact that there is an easy integration with HubSpot, which we use for our Support Desk tickets, so that our Support tickets can seamlessly be linked to development tickets.

What do you dislike about the product?

This isn’t necessarily something I dislike, but it’s an area that could be improved. I understand that Jira is mainly used by developers and naturally has a bit of a “backend” feel, but the interface could be less sterile and dull overall.

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

For our company, Jira provides a reliable way to manage multiple concurrent workstreams across different phases of development. It helps us clearly document requirements and include the information each developer needs when they’re assigned a specific ticket. That same context can then be used by the team member handling QA before release to confirm the completed work still aligns with the original requirements.

Jira also lets us link Support Tickets that require development to the corresponding development tickets, so we can track progress and monitor status. This makes it easier to provide accurate status updates to clients.

What do you like best about the product?

is a very intuitive platform and helps me to organize my team and work with the jira board

What do you dislike about the product?

So far, I don’t think there’s anything I dislike. It’s a great tool that helps me every day.

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

Jira has been helping me organize my work and manage my time better, because I can always see what stage the project is in. I can also share tasks with other team members and receive notifications when someone makes changes. It’s an awesome tool.

What do you like best about the product?

I like Jira software because it allows very smooth internal communication. You don’t always need to log in to the application, and you can communicate very clearly directly from email

What do you dislike about the product?

“What I don’t like is that sometimes it’s uncomfortable to see the entire conversation thread from other people who are in the same project

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

It keeps all tasks organized in one place and makes internal communication much smoother. I can reply directly from email without always logging into the platform, which saves time and helps me stay responsive. It also gives visibility on the progress of tasks and helps coordinate work across team

What do you like best about the product?

Everything appears in a single pane which avoids confusion and helps track all updates in one place. There are no side tickets or scattered threads, so the entire discussion, attachments, and activity history remain visible within the same ticket. This makes it much easier to understand the full context of an issue without searching across multiple threads.

Re assigning ticket is very simple and quick. If a request reaches the wrong team or requires additional expertise, it can be reassigned within seconds. This ensures requests reach the correct owner faster and prevents delays in resolution.

The priority levels such as Low, Medium, and Critical make it easier for the product or engineering team to identify urgent requests. This structured prioritization helps teams quickly separate operational issues from normal feature requests and address time sensitive matters more efficiently.

The ability to paste images directly into tickets is extremely convenient. Screenshots of errors, dashboards, or logs can be shared instantly. This helps explain issues clearly and allows technical teams to diagnose problems faster without requiring lengthy explanations.

The workflow visibility is very strong. Each ticket clearly shows its status, owner, priority, and activity history. This transparency helps teams understand exactly where a request is in the process and reduces the need for frequent follow ups.

The comment and tagging system improves collaboration across teams. Team members can mention specific individuals so the right stakeholders review the issue. This keeps discussions centralized within the ticket instead of scattered across emails or chats.

The search and filtering capabilities make it easy to locate past tickets, track similar issues, and review historical resolutions. This helps teams quickly reference previous work and avoid duplicate investigations.

Ease of implementation is another strong point. The platform allows teams to start using structured ticket management quickly with configurable workflows, custom fields, and permission settings. Organizations can adapt the system to their operational process without needing heavy development effort.

Customer support resources and documentation are very helpful. The support materials, guides, and community forums provide clear explanations for common configuration or workflow questions, making it easier for teams to troubleshoot and optimize usage.

The platform is used frequently throughout the workday because it becomes the central place for tracking requests, reporting issues, and coordinating with product or engineering teams. Having a single operational hub significantly improves visibility and efficiency.

The dashboards and reporting features help teams monitor ticket volumes, response timelines, and recurring issues. This helps identify operational patterns and provides insights that can improve internal processes.

What do you dislike about the product?

One improvement that could make the platform even more effective is clearer and more descriptive ticket statuses. For example, statuses such as Almost Done, Pending Last Leg, Approval Needed from Tech Team or Senior Team, In Progress with Maker, or In Progress with Checker would provide better visibility into the exact stage of the task. This would help client service managers quickly understand progress and communicate accurate updates to clients without needing to review the entire ticket conversation.

The interface can sometimes feel overwhelming for new users because there are many fields, options, and configurations within a single ticket. This can make the learning curve slightly steep for teams that are using the platform for the first time.

Ticket forms can occasionally contain too many required fields depending on how the project is configured. This can slow down the process of raising a quick request, especially when the user only wants to report a simple issue.

Navigation between multiple projects or boards can take time to get used to. When several projects exist within the workspace, finding the correct queue or board may require additional filtering.

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

As a Client Servicing Manager, Jira plays an important role in helping me manage and track operational and client-related issues in a structured way.

Jira provides a centralized platform where product, technology, engineering, and client-related queries can all be tracked in one place. This reduces scattered communication across emails or chats and ensures each issue has a clear record, context, and ownership.

It also creates accountability, since every ticket has an assigned owner, a priority level, and a status. Teams can quickly see who is responsible for resolving a specific issue and what stage the request is currently in.

For critical incidents or urgent client issues, raising a Jira ticket ensures the matter is formally logged and prioritized. This helps the relevant technical or product teams respond faster and makes it less likely that anything important gets missed.

Jira improves cross-team collaboration as well. Because product, tech, and engineering teams work in the same platform, discussions, updates, and troubleshooting steps stay documented within the ticket, helping everyone remain aligned on progress.

From a client servicing perspective, Jira helps me track the full lifecycle of an issue from the moment it is raised until it is fully resolved. That visibility makes it easier to provide accurate updates to clients and manage expectations.

The ability to attach screenshots, logs, and detailed descriptions also helps technical teams understand issues faster. This reduces back-and-forth communication and speeds up resolution.

Overall, Jira improves operational efficiency, transparency, and response time, which ultimately leads to better client support and smoother coordination between internal teams.

Jira integrates well with Zendesk, which helps our team convert customer complaints or incidents directly into Jira tickets for the product or engineering teams. This ensures that client issues move quickly from support to the technical teams responsible for resolving them.

Creating a ticket in Jira is very quick and straightforward. It usually takes less than 30 seconds to raise a ticket, which helps ensure that issues are logged immediately without delaying the investigation and also allows me to clearly explain the issue by adding detailed descriptions, screenshots, and supporting information. This helps my product or engineering teams understand the problem faster and start working on a resolution without unnecessary back and forth communication.