JIRA

Comentarios: My experience has been great with JIRA and I have setup the product in my last two organizations. In my current role, the entire company has moved all their projects to JIRA. Despite some pesky UI bugs here and there, JIRA does everything that I need and has become a critical piece of my day-to-day work. It's never easy to build a product for product people, but JIRA has found a way to do most of what I need. I only wish the business would invest a bit more effort into their support team, but since many companies are already using JIRA, the internet has become a great substitute.

Puntos a favor: JIRA gives me so much functionality out of the box. Within five minutes, I can create a board and invite my whole team to start working with me. It doesn't take long to customize your presentation of work to make it specific to your business. It has become the standard for the industry and with good reason; JIRA gives me everything that I need to track performance and ensure a timely release.

Contras: There are occasionally some annoying bugs that will present themselves, but it's never something that really prevents me from using the product effectively; usually it's an annoying UI bug that looks messy or ugly. For the most part, many of the people that complain about the product just don't know how to use it 'as is out of the box'. The more configurations you try to make, the more problems you can create for yourself. Aside from this, their customer service is quite lackluster and it often takes days if not weeks to hear back from support - usually the bugs are fixed before you even get a response.

Comentarios: We did an extensive search and ended up with JIRA for project management for my team and for our cross-department projects. We've been using it now with our marketing team for several months, and I had previously used it with product teams (developers), and the overall experience is that it provides the best PM experience for our team of all the options out there.

Puntos a favor: They've managed to provide easy to use projects, next-gen, that have most of the power but are SUPER easy to use. We love the new Kanban boards and the ability to turn off features and hide complexity wherever needed.

Contras: The next-gen projects are moving fast, but it feels like at this point you have to choose *either* power *or* ease of use. Classic projects (power) or next-gen (easy) are competing, so I'm hoping they will be able to eventually provide all the power in the easy next-gen projects.

Comentarios: Originally we wanted Jira to be the place for Product and Development. But we soon realised that we needed a separate app for the product team instead. So now the product team work outside Jira and only when it's ready for Development will a ticket get created and planned in the backlog ready for a sprint. Jira helps the Product Manager to know the status of features, bugs and tasks and allows the development team to ask questions relating to the ticket in the comment section. That way there is full visibility of the discussions for future reference.

Puntos a favor: The biggest strength that Jira has to offer is how customisable the app is. We're forever fine tuning how how development flows are setup and I've never run into an issue where what we wanted to achieve could not be possible. The workflow editor is pretty straight forward once you figure out how to map these to specific projects and features. It also has a mammoth number of apps that can integrate with it, which can greatly help simplify your organisations stack. We use a bunch of apps that connect to Jira such as Slack and Git. The mobile app is pretty good and more simple to use. There's also a new iOS app that you can run on a mac that seems to be a slightly faster and more user friendly version. However, I haven't quite worked out how to tailor the notifications. The search is very powerful!

Contras: It is very slow to load pages and jump between stories. When using this on a daily basis it really gets annoying. When we need to change a setting it's hard to work out where to go. I have to say I've never seen another app quite like Jira which has so many different places to go to in order to change very similar settings. If someone accidentally creates a ticket with the wrong type the only way to change it is to Move the ticket. And I can't seem to change the status of the ticket at the same time. So often an Open bug ticket becomes an Open feature ticket, which really should still be in Draft.

Comentarios: We use Jira as a kanban/agile project management tool in software development. The workflow is well understood by most developers and onboarding new team members into our system is a breeze. It is good at tracking projects and managing sprints.

Puntos a favor: As an SDLC management tool it excels. It's designed from the ground up for tracking user stories, tasks, epics, sprints, etc. in large organizations. It is excellent for cross functional team collaboration and really shines in a mature environment that doesn't change frequently or quickly. It is continuously improving and it is obvious that the JIRA team is very proactive and dedicated to staying ahead of the competition in features and services.

Contras: It is overkill for smaller teams or products that are very early in their life. When projects and teams are very dynamic, Jira projects become bloated, cumbersome, and fragmented. This product really is suited for larger, mature organizations that already have strong procedural discipline and rather monolithic approval/decision making. I know it's supporting agile methodology but really it's rigidness is more aligned with waterfall type management.

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.