Mit JIRA bist du immer auf dem neuesten Stand. Ob du Updates per E-Mail, Chat oder über dein Mobilgerät bevorzugst, JIRA ist an seiner Seite. An deinem Schreibtisch oder unterwegs hilft JIRA deinem Team, dank der neuen mobilen Schnittstelle, seinen Job zu erledigen.
Probleme gibt es überall: Aufgaben, Ideen und Anfragen verstecken sich in Dokumenten, in Köpfen der Menschen ... und tief in deinem Posteingang. Nutze JIRA, um die Probleme deines Teams zu erfassen und zu organisieren, Prioritäten zu setzen und Maßnahmen zu ergreifen. So bleibst du auf dem Laufenden und weißt, was um dich herum passiert. JIRA macht all dies einfach und dein Team verbringt weniger Zeit mit der Verwaltung der Arbeit und mehr Zeit mit der Erstellung großartiger Software.
Arbeiten, wie du es wünschst: Dein Prozess steht im Mittelpunkt aller Aktivitäten. Überlasse die Arbeit deines Teams nicht dem vom Projekt-Tracker definierten Standard-Workflow. JIRA verfügt über Workflows, die deinen individuellen Prozessen entsprechen und die du dynamisch an deine Teams anpassen kannst. Verwende das Tool, das zu dir passt und verbiege dich nicht für ein Tool.
Produktive, leistungsstarke Planung: Teams, die effektiv und effizient sein müssen, wählen JIRA, um ihre Arbeit zu erfassen, zuzuordnen und zu priorisieren. Stelle sicher, dass jeder in deinem Team weiß, was getan werden muss und wann – und du erlebst, wie sich die Arbeit reibungslos wie von selbst erledigt. Und wenn du JIRA mit dem JIRA Agile Add-on echte Agilität verleihst, kannst du sogar agile Sprints planen!
Einfach zusammenarbeiten: In jedem Team ist es wichtig, dass Menschen Informationen leicht austauschen und bei Bedarf Hilfe anfordern können. Die einfache, intuitive Benutzeroberfläche von JIRA ermöglicht es dir, mit Teamkollegen zusammenzuarbeiten und die Arbeit effizienter zu erledigen. Wenn du das toll findest, wirst du es noch mehr lieben, wenn du @mentions und Zuordnungsfunktionen von JIRA mit Confluence und HipChat kombinierst.
Sichtbarkeit mit Lichtgeschwindigkeit: Beobachte die für dich wichtigsten Probleme, überwache Activity-Streams und teile Informationen über leistungsstarke Dashboards, Wallboards und vieles mehr. Mit JIRA weißt du immer, was vor sich geht.
Sammeln, Service und Berichte: Mit JIRA Service Desk wird die JIRA-Plattform zu einem modernen, flexiblen Service-Desk-Erlebnis, das Kundenanfragen optimiert und die Effizienz deines IT-Teams steigert.
Agiles Projektmanagement: Heutzutage reicht es nicht mehr, nur die Arbeit im Auge zu behalten – du musst agil sein. JIRA Agile erweitert die Leistungsfähigkeit von JIRA um agiles Projektmanagement.
Overall, experience with JIRA is just awesome.
Simple tool to maintain the team's effort and Project's status on a single page, Project boards.
Would blindly recommend JIRA for simple and complex Agile projects.
Happy Project Tracking :)
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.
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.
My experience with Jira has been fantastic. Overall, once a team gets used to the 'ticketing' structure, there are a lot of organizational efficiencies that can be gained. The standardization of ticketing can help teams navigate through areas of need and allocate resources from other projects if ahead of schedule. Jira works phenomenally as a tool to help manage projects both large and small. I have helped test and implement projects that have utilized Jira as the primary project management tool and believe that it is a state-of-the-art solution. Overall, I cannot recommend this service enough!
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.
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.
It took time to get buy-in from the entire IT department to fully utilize JIRA. However, now that the whole department is all-in, JIRA has truly made our work effort much easier. We now have internal business partners who utilize JIRA to review work status, set priorities, and create new tickets when issues/upgrades present themselves. With an organization our size, I can't imagine not utilizing something like JIRA...not sure how we did it all in the past.
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.
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.
A very strong tool for development projects, which covers so much more than just project management. Thanks to Jira, you can track issues over the whole development life cycle. Entire project layout is possible with infinite iterations, including planning and backlogs. The variety of collaboration tools involved (like comments) is unmatched by all other tools I’ve used. The project progress is easily tracked, plus you can track then across releases. Jira offers full reports on both progress and performance.
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.
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).
In a few words JIRA is a task tracking software that makes life easier when working on a project.
Once the initial setup is in place (easy to do for common scenarios ) all is left for an administrator is to manage the list of projects and user accounts.
Note that parts of the process (e.g.: customizing workflows) need to be done up-front, since this will become more complex once one or more projects are configured and in-use
As for usability, it is one of the best tracking systems I've ever used: as a developer/QA you can easily update the status of your work in a user-friendly way. As a manager, you can always get the overview you need by just opening a screen or a report (most of what you need is in place by default)
What's best about it is that as long as it is installed on-premises, it can be used as a central point of information for everyone involved with a project. The fact that it can be integrated with other common software industry tools adds further benefit from this.
In the end, I should probably add that I've been using all kinds of bug tracking systems for about 15 years (starting with ancient tools like redmine going through PivotalTracker or VersionOne or JIRA) and almost all of them were either missing features that I deemed important or "spartan" usage/layouts that constraint the usage.
JIRA just provides everything that's needed in completing a project out-of-the-box (whether it's Agile, Waterfall or Kanban or whatnot)
- 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
- 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).
Weiter unter folgen häufig gestellte Fragen über JIRA Software.
JIRA Software bietet folgende Kostenpläne an:
Beginnt ab: 10,00 $/Monat
Kostenlose Testversion: Verfügbar
JIRA Software bietet die folgenden Funktionen:
JIRA Software hat die folgenden typischen Kunden:
Großunternehmen, Mittlere Unternehmen, Non-Profit, Öffentliche Verwaltung, Kleine Unternehmen
JIRA Software unterstützt die folgenden Sprachen:
Chinesisch (traditionell), Tschechisch, Dänisch, Englisch, Französisch, Deutsch, Italienisch, Japanisch, Polnisch, Portugiesisch, Russisch, Spanisch
JIRA Software hat folgende Preismodelle:
JIRA Software unterstützt die folgenden Geräte:
Android, iPhone, iPad
JIRA Software kann in folgende Anwendungen integriert werden:
AppFusions, Get Satisfaction, Innotas, LeanKit, SpiraTeam, Testuff, Usersnap, Workfront, Zendesk, time cockpit
JIRA Software bietet folgende Optionen für Kundensupport:
Häufig gestellte Fragen, Forum, Wissensdatenbank, Online-Support, Telefon-Support, Video-Anleitungen