What do you like best about Jira?
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. Review collected by and hosted on G2.com.
What do you dislike about Jira?
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. Review collected by and hosted on G2.com.