JIRA

Comentarios: I use JIRA in all the Agile software development for classification and bug tracking for every user with Dashboards. I am satisfied with the JIRA features but I think JIRA needs to provide more integration towards CICD tools so that user can get more idea about the bug tracking.

Puntos a favor: Easy to create Agile dashboards to track bugs in different development life cycle. We can also extract informations regarding the user specific tickets created and worked for any period of time. Also we can attache documents to gives an entire idea about the the bugs and time tracker in comment section provides how much time it takes to fix the bugs. In the software industry JIRA is one of the widely used Bug tracking platform. The idea of classification of tickets like EPIC,Task are very useful to identify the work load needed for that ticket.

Contras: Need exact date and time of the ticket creation and comments when the ticket gets older, right now it describes like the ticket is "created more two weeks ago". JIRA also needs to integration with CICD tools for more information regarding the bug tracking and fixing. JIRA should provide a dashboard for each user how much time he worked on a ticket to track the overall work time and also it will be very easy for the Administrator also.

Comentarios: THe best software for project management ever.
It's paid, but even for our size of projects, we still love to spend some money on it and enjoy the good project management.

Puntos a favor: Everything ! the software is very powerful, it has a lot of options and features:
- Scrum, Agility and flexibility of changing flows.
- Security setup for every type of users.
- A lot of features ( no way to compare it with any other software i know )
- Very simple to use
- Sprints support..
- High Availability.
- Awesome Designs ( old and new ).
And so many other things i love about JIRA

Contras: I wish the cost was a little more less for small sized companies.

Comentarios: I highly recommend Jira for a bug tracking tool and especially for Agile software teams. For us it has really made a difference in terms of: team collaboration, Agile methodology adoption, decreased time to market of new projects/new features and on the overall teams' spirit. We have seen a wide adoption for the other departments as well, non software development.

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

Contras: 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.

Comentarios: Great software, but I couldn't believe there was no native chat support for assisting with issues. Really Atlassian? Are you that proud of the UI? You shouldn't be... you probably bought Trello because enough people were having a hard time figuring out all of Jira's quirks. Trello is so much easier and faster to get up and running for projects, so that was a good buy. Take notes.

Puntos a favor: The backlog and features for managing the backlog with different methodologies such as Kanban, Scrum, or Kanban + Scrum hybrid are very flexible. Planning sprints, releasing sprints, and looking at history of what was done is very organized.

Contras: Cumbersome to setup. Workflows for issues and UI/UX for creating them is not easy to understand. Sure you can figure it out, but it will require a lot of facepalms. It's good for larger organizations with several cross-functional teams, but if you are a smaller organization stick with Trello and checklists for the cards if sub-tasks are needed. The sub-tasks in Jira are just plain awful to work with, and will end up wasting a lot of time for your team.

Puntos a favor: I love JIRA. I use it professionally and personally. Even though it is primarily a task manager for software development, I have found that it is flexible enough to be used for all sorts of projects. It is amazing how customizable it is; you can configure your project settings to your already existing workflow, whatever it may be. While the initial setup can be time consuming, once you have your settings configured, using the tool is a breeze. It takes seconds to create tasks, start springs, evaluate progress, etc. I find that this makes JIRA standout from other task managers. In most cases, if the software allows for detail-oriented task management the process of inputting and tracking the tasks themselves is cumbersome. Entering and tracking tasks should not have to be another time-consuming task! The JIRA web application is also excellent, making it easy to enter or track tasks on-the-go.

Contras: I think there is a lot of potential with Jira's NextGen projects, however, the software rollout has been uneven and often not well documented. I wish this process would have been better thought out to make transitioning to NextGen projects smoother.