JIRA Service Management

Gestionar estado de tareas y dedicación fácilmente

Puntos a favor:

Permite realizar el seguimiento de los desarrollos, soportes, incidencias de manera sencilla.Permite gestionar el tiempo dedicado a cada tarea por cada integrante del equipo.Permite visualizar estadísticas relativas a cada una de las tareas que están en espera, en curso o finalizadas y comprobar si la cantidad de horas dedicadas es la correcta.

Puntos en contra:

Tiene mucha funcionalidad lo cuál es bueno, pero en ocasiones puede ser difícil encontrar lo que estás buscando.

JIRA una solución completa con infinidades de funcionalidades

Puntos a favor:

Posee muchos módulos que se complementan entre sí, como Confluence para la gestión de Conocimientos.

Puntos en contra:

La segmentación de permisos es demasiado granular, haciendo realmente complejo el proceso de ABM.

De las mejores herramientas de la gestión ágil de equipos

Comentarios: De las mejores opciones para la gestión de proyecto y reducción de tiempos en la gestión de trabajo

Puntos a favor:

Optimiza mucho los flujos de trabajo además de servir en la autogestión de servicios.

Puntos en contra:

Uno puede perderse en las opciones de los servicios

Jira, one of the best ticketing tools

Comentarios: I have been using JIRA and its different versions, distributions, add-ons for a time now.This is one of the best-known yet expensive solution for ticketing, and one of the best working one.You may check what points I have collected for pros and cons, yet if I could, I would use and recommend JIRA.The interface what most people "ragging" about JIRA, indeed needs to time to get familiar with, but Salesforce and its chatter, JIRA is still better.There are training material, some on-boarding also available in-built for JIRA and after a few ticket, you are ready to go on your own.In every sector you can find ticketing tools, JIRA is customizable according to your needs.If a lot of people are going to use it, I recommend to have an on-premise solution with a lot of power.There are rivals to JIRA, even in-house ticketing tools, in my company now we have 2 systems, yet an IT-provider can use a lot of them, causing a chaos.JIRA is continuously being developed, there are 3rd party extensions to it, quite stable.

Puntos a favor:

Can clone tickets, create linked issues Can create parent-child relationshipsOther Atlassian sw. products and modules are well integratedScreenshots can easily be attachedPossible to delegate close bulkily ticketCan mention colleagues to make them remember about the tasksOptions to connect 3rd party developmentsExport modes are greatCan connect an e-mail address for processing

Puntos en contra:

Lack of dark modeRedirecting tickets with the old IDs sometimes weirdScheduled reports could be usefulSimple "User" mode/layout is not enoughUI is not that easy at first, still better then Salesforce.JIRA is a general ticketing tool I would say, but there are others focusing on more on a technical side, like HP SM9.

Life Savior tool for Agile Projects

Comentarios: JIRA is becoming one shop all for all project management needs.
It also act as a tracking warehouse for all project management and IT management activities in current agile world.
Scrum meeting actions and stories are easy to browse compared to other existing tools on premise.
JIRA is also efficient to manage code control versioning easily by rapidly varying requirements.
It saves a huge cost for placeholder for our IT Asset management when migrated from traditional software

Puntos a favor:

JIRA service management is very use friendly software in day to day project activities. JIRA has been excellent tracking tool for testing bugs, defects easily during entire project cycle. It is very effective place holder for IT asset management and project management phases. JIRA has capabilities to integrate with multiple ITSM management tools and reporting tools for effective reports and dashboarding.

Puntos en contra:

New changes for html pages take little more time for loading when moved to production. Version controlling sometimes create hiccups during rollback period.

Alternativas consideradas: Confluence

Razones para elegir JIRA Service Management: JIRA is more user friendly and easy to mange across enterprise compared to Excel. Macros behaviors were pain points during maintenance but JIRA resulted as cost effective tool for corporates model.

Software anterior: Microsoft Excel

Razones para cambiar a JIRA Service Management: It is more cost effective and user friendly software compared to Confluence. It is easy to track for scrum stories and follow agile approach to avoid standard documentation hours