JIRA Software

Vorteile

I have been working on an Agile Project and I would say this is the best tool for the below reasons,
* Better visualization of the project roadmap for the team.
*Customizable options, Kanban and Scrum boards that can be modified as per the project and fields to be displayed, columns on board for the flow of tickets, etc..
* Easy task allocation and tracking, from both Manger's and team members view.
* Allows the user to create/edit respective items, for example making file and screenshot attachments just a click away.
* Integration with other apps used by the project is simple. Namely apps like TestRail & Confluence.
* Best part is the backlog, which helps to create/track ticket then and there when required and work on it in future.
* Viewing logs is easy as every action is tracked.
* Easy filtering options and report generation for project statuses.
* Filter out tickets release-wise, helpful for regression.

Nachteile

For the simplicity of the application, I could hardly think of any major negative points.
I faced this situation so just sharing it. If the team member is released from a project he/she has no option to request via.JIRA to dissociate from the Project Board/unsubscribe from getting emails related to the ex-project. Inbox gets loaded with all the comments and action performed by the ex-team members.

Vorteile

I use Jira for Project Management in my occupation. As a worker in a large enterprise, Jira does a phenomenal job of creating a fantastic user experience for both desktop and mobile. I think mobile project management is especially intuitive with this service. Where Jira stands apart from other standard project management tools is in its ability to track issues throughout an entire development lifecycle. Tickets are an essential component to keeping work organized and teams moving forward. The ability to collaborate via comments is unparalleled. Jira also offers extensive add-ons and pre-created templates for those just learning the service. When tracking projects, I never felt overly-encumbered by high learning curves or a clunky interface. Jira allowed me to work with many of the tools I am comfortable with and expand my potential.

Nachteile

From my experience, the largest pain-point / decision point between my team is on the issue of creating 'tickets'. While Jira is a very detail oriented application, this detail can sometimes become quite cumbersome. For example, the process of creating and resolving tickets can sometimes feel even longer than completing the task itself. Furthermore, it is difficult, if not impossible to close a ticket if you are not the creator. Therefore, project managers need to carry significant oversight as task statuses change. Therefore, tickets are very controversial but also an essential component to completing work successfully on this platform.

Vorteile

The best part about JIRA is the ability to keep track of all work being done via tickets. I love that JIRA works for all kinds of styles of work. We work within an Agile environment, with some teams using Scrum and other teams using Kanban. No matter how the team is structured, they utilize JIRA tickets. This is great because there is a single repository for all work being done and we can easily search for tickets across all the different teams. The use of Epics vs. Stories is very easy too. We can keep track of what tickets belong to which effort with ease and show the progress of work through the tickets. We can also easily maintain a backlog of tickets. If two separate people submit a similar ticket (or at least two tickets that reference the same work effort), we can combine those tickets easily so that we aren't feeling overwhelmed with more tickets than actual work.

Nachteile

The biggest debate among our team members is when it is necessary to create a ticket. JIRA has created a culture of needing to log every little thing, even if it takes just a moment to complete the work. Sometimes, it takes longer to create the ticket than to complete the task at hand. That tells me there is too much reliance on JIRA to report work completed. It causes some in management to show that their department is succeeding simply by the number of tickets completed. But the tickets don't tell the whole story, especially because there isn't a time component to those tickets being completed.

Vorteile

One of the best features I’ve found in Jira is the Workflow editor – I’ve never seen anything like it despite my extensive experience. Some people would say it’s not even that important, however, for growing businesses it’s something you can’t do without. Lots of task tracking is needed all at once, as you can never predict what necessities will arise in a growing company. Jira provides great help with all these issues. Sprints can be structured across multiple tandem-working teams, taking into account their wishes and preferences – either for traditional setups or for newer ones.

Nachteile

Honestly, one thing that was really off-putting for me was the impressively complex layout. The project list is simply huge, and you have to take some time to grasp the navigation and search features. Perhaps, in the next update the developer needs to add the possibility to tag or somehow categorize or classify projects more clearly to make them easily searchable. Otherwise, it takes a bit too much time. The dashboard is simple, but I don’t much like the visualization for reports. You also can’t assign tickets to several people at the same time. Only the person who created the ticket has the authorization to close it, which is quite bothersome. You can’t create columns or tables, and notes exist only for text input. I would also like to see a feature where you can generate turnaround time for ticket closure in an automatic way using reports. Plus if you have a bad Internet connection, there are issues with loading contents (sometimes the loading even stops altogether).

Vorteile

- Overviews & quick access to information
- Possibility to integrate with most commonly used systems (it integrates with pretty much all mainstream tools, nut just the ones from Atlassian) - you can integrate it even with continuous integration tools or test management tools (e.g. TestRails)
- Security control (everything is fine grained, tools to configure fine-grain access are already integrated
- Comes out of the box with the most common work scenarios (client onside/offsite, development only/development + product management, etc)
- Reporting (easy to extract the things that matter (whether this is worked hours or development velocity)
- Version management (easy to manage what features are grouped in a release, or what fixtures were done for which version)
- Workflows can be customized to match just about any real-life usage scenario
- Allows for both on-premises (self-hosted) installation and cloud usage.
- Configurable dashboards

Nachteile

- Pricing - it is prohibitively expensive for small companies, although they are making steps to minimize this with the new pricing models (e.g.: a few years ago they started allowing up to 5 accounts per project and unlimited projects, for a fixed yearly fee).