Opiniones de Jira

Puntos a favor

JIRA es muy completo y siempre que crees que le falta algo, en realidad lo tiene pero no estaba activado. Permite administar las tareas usando SCRUM o KANBAN y ajustar los tableros de manera personalizada. Tiene muchísimas opciones y alternativas, es muy flexible pero un tanto confuso para un usuario inexperto. Posee muchos reportes de sprint y permite segmentar los datos de manera útil. Posee filtros personalizados sobre los cuales visualizar luego la información y nos está resultando muy útil.

Puntos en contra

A veces resulta un tanto lento, creo que deberían remover algunas transiciones CSS que camuflan un poco la lentitud en traer los datos pero dan la sensación de aplicación lenta. Si abres muchas incidencias en pestañas tendrás el CPU a fuego y tardará bastante en cargar.

Puntos a favor

Su mulltiplicidad de features ayudan en la gestión del trabajo diario del equipo. Tiene desde herramientas de estimación como poker planning hasta la consulta de métricas de performance del equipo.

Puntos en contra

En ocasiones y determinadas acciones de usuario resulta poco intuitiva y con comportamientos inesperados en los componentes de su interfaz, lo cual genera incomodidades en el uso. Estos comportamientos se terminan aprendiendo e incorporando con el uso continuo en el tiempo.

Puntos a favor

Es una muy buena herramienta para coordinar y llevar acabo metodologias aguiles de trabajo ya que te permite desde la planificacion, armar sprints, tener un backlog centraliizado y estimar tareas

Puntos en contra

Tiene una curva de aprendizaje media alta, pero mas alla de eso no cambiaria

Puntos a favor

Permite tener el seguimiento en web de las actividades llevar un CRM orientado a productos Web

Puntos en contra

No es tan amigable para tareas independientes dentro de los flujos de trabajo, para hacer modificaciones se requiere hacer ajustes en todo el flujo de trabajo

Puntos a favor

Se puede mantener una organización del proyecto según los roles que tenga cada persona del proyecto

Puntos en contra

Se debe saber utilizar bien el manejo del programa para sacarle todo el provecho

Puntos a favor

Sin palabras es un sistema bastante sencillo de usar, aunque tal vez dejar personalizar colores en los estatus del Workflow sería genial

Puntos en contra

Que no deja personalizar colores de estatus.

Puntos a favor

Lo que más me gusta es que resuelve el problema de gestión de colas y prioridades de las peticiones de desarrollo y mantenimiento de diferentes departamentos de la empresa. Permite agrupar, clasificar y priorizar tareas que nos permite ser más ágiles y centrarnos en lo importante.

Puntos en contra

Quizás la herramientas es demasiado simple. Hecho de menos tener herramientas de seguimiento y aviso de estatus de incidencias proactivas.

Puntos a favor

utilizo esta herramienta a diario para planear mis proyectos y asignar tareas a mi equipo de trabajo, en cualquier momento puedo saber que avances tenemos y puedo dar seguimiento a cada tarea que asigne

Puntos en contra

en ocasiones actualizan la interfaz y se vuelve un poco complejo adaptarse a las nuevas funcionalidades pero siempre son mejoras que a la larga nos ayuda a tener mejor control con la planeacion y administracion

Alternativas consideradas

nTask

Razones para cambiar a Jira

fue mucho mas intuitiva, facil de administrar y el precio esta dentro del presupuesto de la empresa

Puntos a favor

Muchísimas funcionalidades en nuestra empresa tenemos toda la información subida ahí se complementa excelente con Drive y facilita nuestras tareas diarias de manera extraordinaria!

Puntos en contra

La interfaz podría ser mejor, un poco más amigable con los usuarios pensando que sea fácil e intuitiva.

Puntos a favor

Lo que me gustó de Jira es poder organizar mis tareas a Diario para ser más productiva para el equipo

Puntos en contra

Sentí la plataforma bastante dificultosa para manejarla

Puntos a favor

We used several bug tracking tools in the past but Jira is by far the best one. What I like most:
- user friendly interface, provides a nice user experience
- Agile SCRUM/Kanban support out of the box
- extremely configurable on almost everything
- extendable through custom scripting, either built-in or via addons
- very collaborative
- there are thousands of addons in the marketplace; you can even write your own

Puntos en contra

Being so flexible to be configured, the learning curve for admins is a little steep.
The price is based on the number of users and if you experience wide user adoption in a big company, you end up in paying more for upgrading to the next tier, than if you would pay for that tier first time.

Puntos a favor

JIRA has just about every project management aspect covered in their offering and it's easy to set up and configure to suit your needs.
Reporting, ticket tracking, requirement and comment tracking, workflow customization, task assignment and follow-up + more make the life of a project manager a breeze which would otherwise have to be done using a multitude of tools.

Puntos en contra

The permissions structure/permission matrix at the administrative level could be a bit more user-friendly as troubleshooting an incorrectly configured (permission) JIRA instance can be a hassle.
Sometimes when new versions are introduced, some of the older features are dumbed down to make it easier for the user but for power users, this could cause confusion if they were wired to do some tasks using the old methods.

Alternativas consideradas

Asana, Airtable y Trello

Razones para elegir Jira

JIRA was more feature-rich, had all the project management tools needed under one offering and had integrations with a wide set of 3rd party platforms and programs

Software anterior

MantisBT

Razones para cambiar a Jira

More customizable while being user-friendly at the same time.

Puntos a favor

*Functionality

The best feature of Jira is a huge number of integrations, massive amount of possibilities, statistics and tricks that you can you inside the platform.
There is an integrated tracking, kanbans, lists, sorting direct contact with chat (stride) and feature to work with git right from every task or issue.

* New UI

Recently Jira got an update, a new chat (Stride, instead of Hipchat) and a new UI for the tasks. I can see that company goes in the right direction to adopt all of it's powers.

*Customization

Jira, being confusing at first hides a lot of it's features inside most of which you can change and adjust to your business needs. It is a great solution for a big corporation with dozens of departments, hundreds of employees and thousands of issues and tasks daily. However, in all other cases Jira can be a nightmare at this point.

Puntos en contra

*Slow

Out off all CRM platforms and tools to handle tasks and issues Jira is the slowest by far. Is it initial problem or has it appeared after adopting so many technologies under one roof - I can't be sure. But one thing is clear - Jira is awfully slow.

*To many features

Yes, it is a disadvantage when it comes to Jira. When a new customer comes to Jira I believe, he is most definitely confused. Especially, if he/she tried ANYTHING else before. Of course, I see that company does a lot to make it easier and more comfortable, but as it is now, Jira is a terrible solution for fast adoption, scary for a small or middle sized team and most definitely not a great choice for personal use.

Jira is Huge. If you are huge - great features, customizing, different apps and plugins will help you solve a lot with Jira. If you are just starting or don't have that many tasks and issues and people in your company - you should probable check other options.

Puntos a favor

Jira has a weekly release schedule which means the product is always being improved or changed. This is usually a good thing, although I will admit that sometimes it isn't. Jira is also incredibly functional for a broad range of use cases, from managing a simple to-do list, team task tracking, process automation, to software development. They do a good job of making it user friendly and easy to onboard, especially since they started making drastic UI improvements a little over a year ago.

Puntos en contra

A consequence of being capable of so much is that it can be hard to configure initially. More specifically, which features you need and which can be disabled. There are a lot of great features but some just complicate the workflow, and it usually takes time to figure this out.

Alternativas consideradas

Asana, Basecamp, Trello, Wrike, Pivotal Tracker y Teamwork

Razones para cambiar a Jira

Jira was either more user-friendly or offered a solution that was geared more towards software development than the other applications. I also like the direct integration with Confluence, even though Confluence itself can be annoying at times.

Puntos a favor

1. Great User Interface and User Experience.
2. The ability to create custom queues and automatically re-direct issues to these queues saves a lot of time. 3. The inbuilt SLA management and the option of integrating it to third party alert and notification software is impressive.
4. Adding attachment, links and other resources to JIRA ticket is easy and straightforward.
5. It has great audit trail tracking and can act as a source of truth for all parties involved.

Puntos en contra

1. The issue search feature could have been a little more customizable and faster.
2. The options available to format the comments on an issue are limited and not very intuitive.

Puntos a favor

I like the most the integrations available (Bitbucket, Slack, etc) and how customizable the software is. You can define which detail to include in any new created task, project, etc.

Puntos en contra

I liked least the format used for uploading files. With this purpose Jira works together with conduent in a "Pages" format but I would prefer a File Management System based on folders.

Alternativas consideradas

Trello

Razones para elegir Jira

I was looking for a software with more tools alligned with software development processes and tools

Software anterior

Teamwork

Razones para cambiar a Jira

Jira is the most complete SaaS option available in the market for software development team. Their format help teams to adopt scrum.

Puntos a favor

I've been on teams that have used Jira for more than a decade now. Now I manage teams that use it and we certainly get a lot of value out of it. I love the power and infinite flexibility to customize everything to our needs. It's incredibly powerful, fast, stable, and powers all of our cloud, app and firmware deployments/releases by managing the user stories and bugs that go into each release.

Puntos en contra

The user interface is now so complex that we have to employ full time people just to wrangle Jira. The PMs themselves are pretty scared of it and would never try to customize it--the TPMs and Sr. TPMs often struggle to do what we need. It can really take on a life of its own because it's so incredibly complex. We have had to move a lot of project management tasks over to Asana because there are so many things messed up and broken about our current Jira (cloud) instance. Bottom line--don't choose Jira unless you've got SDEs that are super adept at it already. If you're just starting out, it's very attractive pricing, but the complexity will kill you. Go with something easier.

Alternativas consideradas

Redmine

Razones para cambiar a Jira

We chose Jira because it's such a standard and it's very easy to hire devs who have a ton of experience and in fact have never used anything else.

Puntos a favor

It does its job pretty well and that's why it's been used by most enterprise companies. The ability of tracking and sprint planning is very good. I also liked the way it manages the coordination between different teams. It's always very simple to create a JIRA, assign it to the team members and get the task done.

Puntos en contra

UX could be improved a lot. Most of the time I had to use Google Sheet to manage my tasks with JIRA ID. It's mainly because of the complicated UX to manage the product roadmap.

Puntos a favor

Workflow customisation is by far the best of any software that i used. Also connecting confluence pages with jira tickets helps a lot for better documentation.

Puntos en contra

Sometimes it is slow or wont load. Also i have a felling that the state of a ticket changes on its own, but not always.

Puntos a favor

I really like using Jira from Atlassian. I usually use it in the scrum and with the support team to open tickets and solve them. It integrates with a lot of tools and has a lot of plugin-ins that I use.

Puntos en contra

Using it with Kanban as it didn't support all the required features in sophisticated board design in Kanban.

Alternativas consideradas

Kanbanize

Razones para cambiar a Jira

It is simpler and has a lot of plugins and integration. Simpler and to the point.

Puntos a favor

So far, the gold standard in project and process management, especially in the number of options, features, automations, integrations and workflows that the software is capable of handling. We shifted to this software when the pandemic hit and were forced to stay at home since we needed a more powerful software to handle our workflow. If you have a techy team, nothing else compares.

Puntos en contra

Biggest con really is that it is not the most user friendly software. Unlike Trello or Asana where you can just go fire it up and it's good to go. This one takes a lot of set-up to do and a deep familiarity with how it works under the hood. Given that the software is one of the older ones, you can sort of see it's age in both the older workflows (issues, screens, etc) vs the newer templates. The newer project templates sort of partially solved this problem but if you need to tweak the settings, it still has a steeper learning curve.

The con really here is that i tried Jira with my other less techy company (a school) and adoption was really low as users just weren't able to keep up with it.

Alternativas consideradas

Asana, Teamwork y monday.com

Razones para elegir Jira

Needed something more powerful

Software anterior

Trello

Puntos a favor

1. Different user roles can be defined to allow for segregation of duties.
2. Epics can be defined to assist with long and intermediate project planning.
3. Duration of sprints can be defined according to project requirements.
4. Statuses for user stories can be used for tracking progress as well as workflow management.
5. Allows for bulk import of epics and user stories which can fast track administrative tasks where this information has been captured elsewhere e.g. CSV format

Puntos en contra

1. Only users from within the organization can be assigned to tasks and user stories. This can cause unnecessary delays where external users need to provide urgent input or contribution.
2. Statuses (user stories) cannot be defined specifically for a board where multiple boards exist within a project.
3. Only two types of users can be assigned to user stories, which are assignees and reporters. JIRA does not allow for multiple users (assignees) to be assigned to one user story.

Puntos a favor

I like the kanban board, it works very well and looks simple to use (but it's not easy to setup). The task management for business project is very nice and the new feature of being able to look at the overall work like in a spreadsheet, definitely beats Smartsheet for me. I like that you can easily move your work when you're done using the board view, if you like.

Puntos en contra

Scrum/Agile can be difficult to setup because the Kanban board isn't so great when setting it up. I have run into some difficulties with it, their support board was helpful but it did not resolve the issue.

Business projects do not have the ability to link to Bitbucket, it would have been nice to include task management with Bitbucket integration, it helps to appropriately follow up on tasks.

The board view for tasks and sub-tasks doesn't work for me. I'd like to see that there are major tasks with steps of the child tasks (change the subtask icon too).

Alternativas consideradas

Smartsheet

Razones para elegir Jira

Atlassian has a wider product range and it helped to keep everything with one organisation. Secondly, at the time, JIRA integrations with other tools we used, worked really great.

Software anterior

Asana

Razones para cambiar a Jira

There were some drawbacks with Smartsheet when we used it for a short time to try it out. Some liked it but my team and I preferred JIRA and we were the decision makers.

Puntos a favor

JIRA is one of the best, simple, and user friendly project management tool. We have been working for almost 3 years now and the user experience it offers is applaudable. You can create your agile boards for scrums and can go KANBAN as well. You can create as many different teams and squads. Link your issues to stories and trace it to the feature, Track how much effort is being spent on an item; Track for how long an item has been been sitting idle; Prioritize your issues, backlogs; Create dashboards for ease and convenience; generate reports, traceability matrix, velocity burndown charts; add/remove user access. You can customize it as per requirement and with ease. Recently it has moved to cloud, so down time has been relevantly decreased which is an added bonus. Best part I like about using JIRA is that its very easy to handle, we can do bulk update on items and it takes very less time to understand. This is one of the best tools that is out there and I believe almost every organization is using it.

Puntos en contra

There is nothing much to add in this section. Practically I am all thumbs up for JIRA. I have a suggestion though. JIRA needs to have a Instant Messaging option enabled so that an organizations do not need to look out for a separate tool. I think if Atlassian would be able to achieve it, not only they would be able to enhance their customer base but they would be able bring a lot revenue.

Puntos a favor

It's a very powerful tool. It provides many advanced features to collaborate with people. We can easily tracks things on Jira through our mobile devises and other gadgets. It helps us to plan the projects with tasks and sub-tasks.

Puntos en contra

It is an expensive software compared to other open source software. I have worked with many software Jira is one of the most expensive product that we have used in our projects.

Alternativas consideradas

Asana, HubSpot CRM y Salesforce Sales Cloud

Razones para elegir Jira

Salesforce was not suitable for our requirement and the type of business that we are doing. So, we have shifted to Jira and it's a very important decision for us to collaborate our exciting team.

Software anterior

Salesforce Sales Cloud

Razones para cambiar a Jira

Jira is developer friendly, easy to work with, easy to collaborate with multiple people on the same task, have features to same attachments and issue tracking with notifications is very helpful to complete tasks on time.