Jira Erfahrungen

Vorteile

Wir nutzen Jira in unseren Scrum Teams für sämtliche Projekte. Sowohl der Projektfortschritt als auch die Planung funktioneren mit Jira sehr gut. Tickets können in Story und Tasks aufgeteilt werden und jedes kann ein eigenes Zeitkontingent bekommen. Ebenso lassen sich manuelle Tests hier sehr gut dokumentieren mit dem Plugin XRay.

Nachteile

Filterfunktionen kompliziert technisches Tickets lassen sich nur als Tasks abbilden

Vorteile

Der Weite und der Unfang der Applikation. Ist einfach echt Top und Sehr durchdacht.

Nachteile

Nein, es gibt für mich keine negativen Punkte. Nag sein das es welche gibt, bis jetzt aber nicht die Erfahrung damit gemacht.

Vorteile

Implementiert Standard-Vorgehensweisen in der Softwareentwicklung und bietet einfache, leicht verständliche, grafische Oberflächen für den Benutzer.

Nachteile

Die Administration von Projekten ist oft etwas unübersichtlich bzw. lassen sich Einstellungen oft schwer finden.

Vorteile

Man kann damit wirklich komplexe Vorgänge planen und verfolgen sowie verschiedene Tasks untereinander verknüpfen. Finde es sehr intuitiv in der Anwendung. Steigert definitiv die Produktivität und verbessert die Zusammenarbeit in unserem Team.

Nachteile

Manchmal kommt es zu Problemen wieder zurück in die Webanwendung zu kommen, wenn man verknüpfte Dokumente aufruft - kann aber auch Anwenderfehler von meiner Seite sein... Aber das passiert eher selten und ist auch keine große Sache.

Vorteile

Einfache Benutzung, kompakte Übersicht, großer Funktionsumfang, mehrere Schnittstellen

Nachteile

Man wird oftmals mit Mails überflutet wenn man die Standardeinstellungen verwendet. Sehr viele Einstellungsmöglichkeiten können anfangs oft etwas schwer zu verstehen sein.

Vorteile

Übersichtlichkeit, leicht verständlich, einfach zu bedienen.

Nachteile

Front-End ist etwas langweilig gestaltet

Vorteile

schnelle Bereitstellung und gutes Preis-Leistungsverhältnis

Nachteile

schwierig bei Einhaltung DSGVO und ISO-Norm-Umsetzung

Vorteile

Es ist eine solide Software. Ist auch benutzerfreundlich. Die Sicherheit der Kommunikation ist auch gut vorhanden.

Nachteile

Die Oberfläche sieht nicht so modern aus, aber es ist nicht so relevant.
Bin nicht sicher, ob sich damit auch agile Projekte gut verwalten lassen.

Vorteile

Die Planung meiner Projekte und die Einteilung von Aufgaben (zeitlich und personell)

Nachteile

Übersicht ist am Anfang sehr gewöhnungsbedürfitg

Vorteile

Die Kanbanfunktion. Die ist sofort verständlich und einsetzbar.

Nachteile

Die schwierige Handhabung für alle, die keine Zeit haben, sich großartig einzuarbeiten. Dies erfolgt dann zwangsläufig in der Freizeit...

Vorteile

Unerlässlich für einen sauberen Sprint Plan, die Abbildung von Workflows und Prozessen ist sehr gut

Nachteile

Silo zwischen Jira (IT) und anderen Tools (zb Asana), hier wäre eine API wünschenswert

Vorteile

It has plenty of features out of the box. It has multiple layers (Teams, Projects) that can support the organization of the whole company, establishing enough separation, but at the same time, the right integrations between the different teams within the company. Can be easily integrated with the whole Atlassian universe (Bitbucket, Confluence), and I truly recommend doing so as you will have every single possible place to put any part of your project (code, backlog, sprints, documentation). It gives you all the needed tools to handle any Scrum or Canvas team, although you will take more advantage of using Scrum I must say. It can be easily integrated via code, and make very creative automated build ticket systems.

Nachteile

It's pricy and having a lot of free options out there that can handle multiple people, it's hard to say that is the right tool for small indie teams. It is indeed the right one for companies, but for low-budget teams.. it's probably safer to go with free options that don't limit the members' amount.

Vorteile

Jira's interface is intuitive and easy-to-use, making it the perfect tool for project management. It has powerful features such as issue tracking, project planning, and workflow customization that allow teams to collaborate and get projects done fast.

Nachteile

Jira can be expensive for some teams, especially those with multiple users. Additionally, the learning curve to use the software can be steep and some customization features require advanced technical knowledge.

Vorteile

Since it is the mainstream product in the market and Atlassian has other powerful tools, the integration with first and third parties is guaranteed and are usually pretty good (ex. Confluence, Slack, Gitlab, TeamRetro...)

Nachteile

After more than 10 years using JIRA for project management I have to say the UX still terrible, the changes and new features took ages to be implemented, and still have too many unresolved issues. If I have to choose a pain point, dashboards are really really painful to craft, and is really easy to face simple limitations that require a paid plugin to allow you to get what you need.

Vorteile

One of the greatest advantages of using JIRA comes with the prioritization of activities since it allows us to remove subjectivity when executing tasks that are really more important. With JIRA we will achieve that critical tasks are carried out in the shortest possible time and the evidence of the execution is recorded, on the other hand, the platform is fully configurable for any type of project or organization, which avoids the need for custom development or integrations made for a specific need.

Nachteile

When interacting with JIRA in a corporate environment, it's easy to configure and customize user views, roles, and permissions, and it's very easy to get familiar with the user interface and menus, making task management intuitive. On the other hand, collaboration functions to communicate with the team, as well as the notifications, keep employees and senior management informed, regardless of the type of organization, we can use it to track projects.

Vorteile

The flexibility to choose the method of project management you wish to use. Also, the ability to customize features to suit your needs is enormously powerful!

Nachteile

During the implementation phase, be aware that each and every ask is an additional charge.

In Betracht gezogene Alternativen

Asana und Zendesk Suite

Gründe für den Wechsel zu Jira

Jira, JITSM, and Confluence provided us with the most comprehensive package for our needs.

Vorteile

The number of features like task creation, epic creation, and story creation which makes it very easy to use in a versatile way

Nachteile

One thing I want that needs to be improved is the interconnectivity of the features like you should have a direct connection of epic from the task.

In Betracht gezogene Alternativen

GitHub

Gründe für den Wechsel zu Jira

Jira has more features than any of its competition.

Vorteile

Software is easy to use and it makes it efficient to monitor the progress of projects and tasks. In addition, the software is good for projects and tasks, because you can put road blocks and reasons why a task has not been successful or progressed according to the schedule, for example. In addition, you can assign importance ratings to all tasks, which creates schedules for the importance of doing tasks.

Nachteile

Softa has a lot of different elements that can be used for different projects and tasks. In addition, different teams may have different ways of monitoring projects from the board, which may cause confusion in the management and monitoring of projects between different teams.

Vorteile

Jira is very easy to use and very simple UI where any user can work swiftly. Jira has helped us a lot as a ticket tracking system as well as Managing our Sprints in the Project Road maps. You can integrate various apps very easily.

Nachteile

Some of the features like planning vs Actual working charts should be there for the older sprints where we can measure the story points of a particular user.

In Betracht gezogene Alternativen

Trello

Vorteile

PO can be challenging, but JIRA has a easy to use UI with a lot of powerful add ons like integration with git and others.

Nachteile

Training can be challenging at first, as you need to be already familiar with SCRUM methodologies

Vorteile

It is a well-established Project Management tool which helps us to plan and keep a track of Project cycle.Issue tracking is most helpful feature in Jira.

Nachteile

It is a great tool, for some of the tickets there is no delete option but I think its a bug which can be solved.

Vorteile

Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.

Nachteile

The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!

In Betracht gezogene Alternativen

Trello, monday.com und Asana

Warum Jira gewählt wurde

Basecamp was rudimentary and unable to effectively visualise our cross-company/cross-team workload.

Zuvor genutzte Software

Basecamp

Gründe für den Wechsel zu Jira

Jira was the most aligned with our internal development workflows and flexible enough to work for both technical and non-technical users.

Vorteile

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.

Nachteile

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.

Vorteile

1) Releases/Versions:
Releases allow us to work in parallel on multiple efforts with the same team.
2) Parallel Sprints:
Same as releases, we are a lean team and we have to work on Product features and polish/bug fixes simultaneously.
3) Custom Filters: I like these the most!

Nachteile

They have taken out small pieces of functionality and made them separate products. These products are now paid and for those small pieces of functionality, you have to make extra purchases. e.g. Pages

In Betracht gezogene Alternativen

GitHub, Trello und Asana

Gründe für den Wechsel zu Jira

JIRA is complete suite for base requirements for development. If you are using Bitbucket for holding your repos then it makes the most sense as well. Atlassian has done a great job with a niche market of software in mind and even though it may seem like an overkill to use it for projects outside the engineering, it is still the best choice for engineering.

Vorteile

Jira is very flexible and can be used for different use cases, eg: project management, issue tracker, road maps etc.
It is quite easy to configure compared to other generic project management tools.

Nachteile

The transition from old user interface to new one, it is very confusing, the UI is not consistent when we visit URLs from email notifications.
Compared to other generic tools, Jira is quite easy but still it is not easy to setup, it takes quite a few days to configure the system as per needs. It would be great if there were boilerplate templates.

In Betracht gezogene Alternativen

YouTrack

Warum Jira gewählt wurde

Pivotal tracker is very specific for project management, we needed a customisable product which we can use with our existing workflows.

Gründe für den Wechsel zu Jira

JIRA was easy to configure and had all the plugins we needed, it was just plug and play.