Avaliações e Detalhes do Produto Jira

O Jira é a verdade suprema que transforma a energia caótica dos post-its em um fluxo de trabalho simplificado e de alta visibilidade. Sua robusta capacidade de personalização permite que as equipes moldem cada problema e quadro às suas necessidades específicas. Além disso, a forma como integra dados técnicos detalhados com o acompanhamento de projetos em alto nível o torna a ponte perfeita entre o trabalho de desenvolvimento granular e a estratégia de visão ampla. Análise coletada por e hospedada no G2.com.

A complexidade pura de sua configuração pode transformar uma configuração simples em um labirinto de permissões exclusivas para administradores e configurações ocultas. Frequentemente sofre de atraso perceptível na interface do usuário e fadiga de notificações, onde o volume puro de alertas pode enterrar o trabalho real. Em última análise, muitas vezes parece superdimensionado para equipes menores, exigindo mais tempo "alimentando a ferramenta" do que realmente enviando código. Análise coletada por e hospedada no G2.com.

The ability to divide user stories into multiple work items like tasks, subtasks, bugs is really useful. It helps with granular control and visibility of the work being done in the team. The ability to add story points further help in calculating the work effort being put in by individual members. The integrations with slack help us with seamless communication and context switching. The performance has never let us down and is industry leading. The recent addition of AI features has further made life easier with auto creation on tickets with just a simple click of a button in slack. Análise coletada por e hospedada no G2.com.

The sprint boards can get a bit overwhelming at times and the work items hierarchy can get confusing. The UI could do with some color as the monotone currently can make finding things feel like finding a needle in a haystack. Análise coletada por e hospedada no G2.com.

i am working as a salesforce consultant and using Jira to manage project delivery, track requirement and coordinate between business, development and QA teams, i like is its strong workflows customization, i can design processes for requirement, development, testing and deployment based on client needs, Jira is very effective for tracking user stories, bugs and tasks, especially in agile project it provides clear visibility of progress across teams. another major advantage is end to end traceability, i can track requirements from business needs to development and testing, which is very important is salesforce implementation. it has large integration ecosystem, allowing connection with tools like Github, slack and CI?CD pipelines. Análise coletada por e hospedada no G2.com.

i dont like its cost increase due to add ons, since many features like time tracking or advanced reporting require marketplace, apps. performance can become slow for large projects or heavy usages affecting productivity, it also require significant admin effort to configure workflows, permissions and fields properly. another drawback is cost increase due to add ons, since many features like time tracking or advanced reporting require marektplace apps, performance can also become slow for large project or heavy usage , effecting productivity. Análise coletada por e hospedada no G2.com.

I appreciate how Jira greatly improves visibility, accountability, and coordination within our team. Its structured approach to tracking tasks, bugs, and project progress helps us deliver projects on time. I find Jira's strong issue tracking and highly customizable workflows particularly useful, especially with its seamless support for agile, which is very effective for managing multiple large projects. I also really like Jira's seamless integration with other tools, such as GitHub. This integration provides a unified view within Jira where we can easily track what developers have worked on, check the success of builds, and see pull requests, which greatly enhances our workflow. Overall, Jira's integration capabilities and customizable features stand out to me. Análise coletada por e hospedada no G2.com.

Yeah. So as I mentioned, it can feel heavy and complex, especially for new users. Our customization can make workflows hard to manage, and the UI sometimes feels cluttered. Análise coletada por e hospedada no G2.com.

What I like best about Jira is how it brings structure and clarity to complex workflows while still being highly customizable.

On the UI/UX side, the Scrum and Kanban boards with drag-and-drop make task tracking very intuitive. I’ve personally found that organizing tasks into sprints and visually moving them across stages helps reduce confusion and saves time during daily standups.

Integrations are another strong point. Jira connects smoothly with tools like GitHub and Slack, which means updates from commits, pull requests, and team discussions are all linked in one place. This reduces context switching and keeps the whole team aligned without extra effort.

In terms of performance, it handles large projects reliably, and I rarely face major slowdowns even with many issues and users.

For pricing and ROI, while it might feel a bit expensive for small teams at first, the time saved through automation, organized workflows, and better team coordination makes it worth the cost. It reduces manual tracking and improves overall productivity, which directly impacts delivery speed.

Support and onboarding are also solid. There’s extensive documentation, templates, and community resources that make it easier to get started, even if you’re new to project management tools.

Regarding AI and intelligence, Jira has started introducing smart features like automation suggestions and predictive insights, which help in prioritizing tasks and reducing repetitive work. Even simple automation rules (like auto-assigning or status updates) have a noticeable impact on efficiency.

Overall, Jira stands out because it combines flexibility, strong integrations, and intelligent automation to improve workflow and team collaboration in a very practical way. Análise coletada por e hospedada no G2.com.

One of the main things I dislike about Jira is that the initial setup and customization can be overwhelming, especially for new users. While the flexibility is powerful, configuring workflows, permissions, and issue types often requires time and experience, which can slow down onboarding.

From a UI/UX perspective, the interface can feel cluttered at times, particularly when dealing with large projects or heavily customized boards. It’s not always intuitive to find certain settings, and this can impact productivity until you get used to it.

In terms of performance, Jira can occasionally become slow when handling very large datasets or complex filters, which affects the overall experience during peak usage.

Integrations are strong, but managing them can sometimes be tricky. For example, syncing with tools like GitHub or Slack may require additional configuration or troubleshooting to get everything working smoothly.

Regarding pricing and ROI, it might not be the most cost-effective option for small teams or startups, especially when adding multiple users or premium features. The cost can increase quickly as the team scales.

Support and onboarding are decent, but resolving specific or advanced issues sometimes depends heavily on documentation or community forums rather than direct support.

As for AI and intelligence, while there are some useful automation features, the AI capabilities still feel somewhat limited compared to what could be expected. More advanced insights or smarter recommendations could further improve productivity.

Overall, Jira is very powerful, but its complexity, occasional performance issues, and pricing structure can be challenging depending on the team size and experience level. Análise coletada por e hospedada no G2.com.

Jira is an excellent tool for company-wide project management. We have a large product and engineering team, and it’s been great for managing work, tracking dependencies, and coordinating across multiple teams and spaces. Smaller improvements - like inline editing and the ability to add epics directly from the backlog view - have also made using Jira much faster and more seamless day to day. Análise coletada por e hospedada no G2.com.

Jira has so many features and capabilities that it isn’t always straightforward or clear (a) where to access them and (b) what’s available or how to set things up. I’ve been using Jira for about six years now, and I still sometimes struggle to get to what I need; it can take me a minute or two to find the right place and figure it out. Análise coletada por e hospedada no G2.com.

Jira is an outstanding tool for QA and development teams. The customizable workflows allow me to create tailored defect management processes that match our testing lifecycle. I particularly appreciate the ability to create custom issue types for bugs, test cases, and improvement tickets. The sprint board and backlog management make it easy to prioritize testing tasks, and the integration with tools like Selenium and CI/CD pipelines streamlines our automation workflows. The JQL (Jira Query Language) is extremely powerful for filtering and reporting on test coverage and defect metrics. Bulk editing and linking related issues saves significant time during regression cycles. Análise coletada por e hospedada no G2.com.

The performance can be sluggish when dealing with large projects that have thousands of issues. Page load times for complex dashboards and filters can be frustrating during busy sprint periods. The configuration complexity is steep - setting up advanced workflows, permission schemes, and notification schemes requires significant admin expertise. The pricing model has also become increasingly expensive, especially for smaller teams. Additionally, the mobile app lacks many features available in the desktop version, making it difficult to manage tickets on the go. Some of the new UI changes in the cloud version feel unintuitive compared to the server version. Análise coletada por e hospedada no G2.com.

It creates a consistent rhythm for how work moves across teams. It makes it easy to break down large features into manageable tasks, which helps during planning and execution. I like how workflows can be tailored to match how teams actually operate instead of forcing a fixed structure.

The backlog grooming experience is strong, you can prioritize, reorder, and refine work without losing context.

Notifications and activity tracking keep everyone aware of updates without constant follow-ups. It works well for both short-term sprint work and long-term tracking of ongoing issues. Análise coletada por e hospedada no G2.com.

Jira can feel cluttered if too many fields or customizations are added.

Navigation between boards, backlogs, and reports can sometimes feel slow. It takes time for new team members to get comfortable with the interface. Análise coletada por e hospedada no G2.com.

O Jira proporcionou à nossa equipe de desenvolvimento total visibilidade de todas as etapas envolvidas na entrega do software, incluindo o refinamento do backlog até a implantação, devido ao seu sofisticado rastreamento de problemas e fluxos de trabalho que podem ser personalizados. O planejamento de sprint e o roadmap também são especialmente úteis, com a capacidade de estabelecer cronogramas alcançáveis e monitorar nosso progresso em relação aos objetivos sem precisar usar ambas as ferramentas. A conectividade estreita com o GitHub e o Confluence tem sido um divisor de águas e nosso código, documentação e gerenciamento de projetos foram vinculados uns aos outros em um único ecossistema integrado. Análise coletada por e hospedada no G2.com.

A interface do Jira pode parecer lotada, especialmente para novos membros da equipe, que demoram muito para serem integrados e aprenderem a navegar e usar o Jira com segurança. A configuração inicial também pode ser avassaladora, pois o número de opções de configuração e definições pode ser esmagador, às vezes necessitando de um administrador dedicado para lidar com permissões, fluxos de trabalho e estruturas de projetos de forma eficiente. Análise coletada por e hospedada no G2.com.

Muito flexível para usar. Você pode configurá-lo para corresponder à forma como sua equipe trabalha—seja Scrum, Kanban ou algo personalizado. Também não é apenas para desenvolvedores; equipes de QA, produto e até mesmo não técnicas podem usá-lo sem muita dificuldade.

Acompanha tudo em um só lugar. Você pode seguir uma tarefa do início ao fim—requisito → desenvolvimento → teste → lançamento—o que torna a coordenação muito mais fácil, especialmente em equipes maiores.

Funciona bem com outras ferramentas. Ele se integra perfeitamente com ferramentas como Git, pipelines CI/CD e aplicativos de colaboração, para que tudo permaneça conectado e atualizado.

Relatórios e painéis úteis. Recursos como gráficos de burndown, relatórios de sprint e painéis ajudam as equipes a se manterem no caminho certo e a tomarem melhores decisões.

Ótimo para gerenciar tanto projetos pequenos quanto grandes. No geral, é uma ferramenta forte quando você precisa de processos claros e rastreamento confiável em escala.

Recursos de IA: A integração com o BrowserStack permite a criação e execução fácil de casos de teste usando IA.

Grande suporte da equipe Jeera. Análise coletada por e hospedada no G2.com.

Com projetos grandes ou muitos dados, pode ficar lento ou travar. Navegar entre quadros, filtros e problemas nem sempre é suave, especialmente para usuários não técnicos. Configurar fluxos de trabalho, permissões e campos pode levar tempo e esforço. É fácil complicar demais as coisas se não for bem gerenciado. Análise coletada por e hospedada no G2.com.