Jira Erfahrungen

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

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

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

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

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

Front-End ist etwas langweilig gestaltet

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

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

Before using Jira, I found it difficult to keep my team's tasks organized in a neat and visually friendly way. In addition, it provides me with many tools that help create a more productive and efficient team, and generates reports that show if the team is making real progress.

I consider that the price can be a barrier to entry when planning whether to decide to purchase the software or not, which can deprive many users of trying this wonderful tool. Also, the support one receives for the product sometimes does not solve the problems one may have while using the software.

1) Integrate seamlessly with development tools like Slack, Github, or Bitbucket.
2) Workspace is very configurable; you may customize the components of each task on your board, as well
as create your own icons, labels, and automated processes.
3) Connect all issues/tasks to Epics and view the anticipated outcomes in the Product Roadmap.
4) It offers the flexibility of a kanban board, which provides the user with a clearer view of what has been accomplished, what is in process, and what remains.
5) User story statuses may be used to monitor progress and control workflows.
6) Allows for bulk import of epics and user stories, which speeds up administrative duties if this information was previously recorded in another format, such as CSV.

1) Only internal users may be allocated to tasks and user stories. This might result in unnecessarily long delays when external users want immediate input or participation.
2) When many boards exist within a project, statuses (user stories) cannot be established explicitly for each board.
3) User stories may be assigned to just two categories of users: assignees and reporters. JIRA does not permit the assignment of numerous assignees to a single user story.

Well, the basics. Assignments, delegations and being able to reply to the assigner and to the client him/herself.

I'm a UX/UI Designer. So, the workflow is convoluted. The interface needs proper blockings because there are so much thing happening on the main page. Take a look at Monday.com for comparison.

This software is very easy to manage day to day work,progress,assignments and forcast for different phases of projects..It turned out to be very effective tool in order to achieve efficient and cost efffective operational model in enterprise organizations

This software should have most reporting widgets and open integration ports so that various data connectors can be integrated for limitless reporting

It's rich in features it offers and it's amazingly configurable, two organizations can have Jira installations that are nothing alike!

It's not a big issue for me, but I think they should offer more best practices in terms of templates for less experienced users to save them from headaches - they are already taking steps in this direction.

Since it's a very large product there are some inconsistencies, doing the same thing in two different parts of Jira can feel like a very different experience.

As we work in the RPA Team, API integration is the best part of JIRA offering, but also overall project management with Scrum and Kanban has proved to be really useful for us.

The UI could be made a little simpler and UX can be improved especially with access controls and resource access management. The charts of Scrum and Kanban board also tend to fly away making it hard to understand and sometimes adds in extra effort for the managers or scrum masters.

Jira is the most complete, stabilized and user-friendly software among many similar software on the market. Thanks to the support of the mobile application, you can follow your teamwork or individual progress wherever you are. Jira is a unique product for professionals.

Unfortunately, we do not have the opportunity to add features for each newly added 'issue' in the 'Board' section. It would be a great opportunity to have this feature, even if it didn't cost Jira much. After adding the 'Issue', of course, an 'issue' related to a great user interface can be edited, but there is no such interface at the time of adding.

- Easy for devs to understand
- Easy to integrate with bitbucket
- Easy to integrate third party apps like slack, zephyr and many more
- Help employees to manage their tasks and track their production time
- Help management to keep track of progress of the project and also to get an idea of employee's performance.

A bit lengthy tool, for new users, one should be able to use it once s/he will spend 1 month on it.

Jira is constantly being improved for the better and Jira 2 years ago this is a completely different product than now. I like the ease of task management and as the other Atlassian products here are closely integrated.

1) Settings are not always obvious.
2) With a large number of automation and integrations, the system has been slowed down.

We used Jira every day for development and Product management for creating, assigning and updating tickets ,user stories and tasks.

Though it's A very useful and easy to use and riched with features but scrum methodology I think Azure devops board is far better in sprint management

I adore the format, checking history. Being able to channel the assignments. And we are ready to see each comment's points of interest just like the correct date. Moreover it is truly simple drag a report Being able to open the task in a modern tab is additionally so precious. Attaching cards to each other moreover makes things simpler.

Some of the time due to the stack of errands we are taking care of it may allow us difficult time stacking a entirety page. When you attempt to look something within the look bar, it may evacuate some of the letters you're writing down may cause typo otherwise you have to be compose down the precise thing to find the right issue.

JIRA is one of the best known software used to develop and track software using the Agile method. Using JIRA is easy to track application usage and easy to assign to developers tasks. I have been working with JIRA in software development for over 2 years. At JIRA we used to develop software on the basis of continuous integration and continuous development.

Honestly, I haven't found a feature or functionality of JIRA that I dislike because it comes with multiple features that are really useful when communicating on a project with team members on the stories.

Quick and easy management and organization of my backlog tasks, the flexibility of setting up almost any integrations for bug tracking with ease, works flawlessly when used alongside other Atlassian products like Confluence. Best pricing options seen till date. Overall takes my agile workflow to the ultimate level with the amount of extensiblity that is second to none in my opinion!

At times there is some flakiness in the outcomes of the actions but generally not a lot worrisome. Also the availability, although can be improved using a private cloud probably, does suffer some occasional hiccups here and there. The bug tracking is comparatively the most improvable area i suppose. It is good don't get me wrong, but can be so much more better with just a few tweaks here and there that's all.

Overall, I really like the flexibility that Jira provides. The one feature that I most appreciate when I use another PM tool is built-in support for Fix Versions. Being able to assign a fix version for a sprint and for each build, makes it easy to see all the tasks and bugs that are in a given full release or an individual build.

A lot of folks, especially artists, have a general disdain for the Jira UX. It is not as ergonomic, clean, and tactile as Trello or Basecamp. I would love it if there were a way for Boards in Jira to be as simple and powerful as boards in Trello.

JIRA permits groups to envision and comprehend assumptions for when to convey an undertaking, have knowledge into project/group/individual limit, and track stay at work past 40 hours.

In a remote-first world, JIRA permits you to keep up with tight correspondence and adjusted degrees even as groups work across time regions.

JIRA is extraordinary for having the option to sort out the extent of significant elements or item dispatches in a manner that can be imagined across groups.

There is an expectation to absorb information to working in JIRA, it isn't quickly instinctive to another client. It normally requires a great deal of learning to most actually and ideally use JIRA. A great deal of it accompanies time and experience.

There are a ton of extravagant accessories in JIRA. It's truly incredible that you can mark or coordinate tickets in a wide range of ways. It is truly dependent upon the association to make a technique for getting sorted out inside those extravagant accessories. This implies each time you go to another association, there is a great deal of cross-over, however, you are gaining some significant knowledge of new techniques and best practices too.

Jira is out of the box free, and it's amazing because it works with everything by the same company. It also allows for easy organization of projects and silos, which intersect with each other. You can easily hand off tasks and allow people to collaborate.

Jira has a very development based angle, so if you're trying to manage a hybrid team, it works well. But if your team is marketing heavy, it's very anti-user friendly unless a person has familiarity with code or databases. It's just sparse and less user friendly.

I find this software to be very versatile and useful.

It has functions that make work easier when it comes to organization, planning, and meeting goals.

It facilitates effective teamwork; it is simple to keep track of the activities that must be completed and the notifications of changes to any action work well.

It has multiple views and is used to manage projects, so people who want to see an overview of the work can use the To-do List or simply the Roadmap, and team members who are trying to balance their daily activities can use the Dashboard to plan their workload.

I like it because it easily adapts to what you want to do.

In some circumstances, receiving notifications has become difficult, preventing real-time monitoring. Although simple and adaptable, defining and organizing the sorts of work items might be difficult at first.

JIRA has just about every project management aspect covered in their offering and it's easy to set up and configure to suit your needs.
Reporting, ticket tracking, requirement and comment tracking, workflow customization, task assignment and follow-up + more make the life of a project manager a breeze which would otherwise have to be done using a multitude of tools.

The permissions structure/permission matrix at the administrative level could be a bit more user-friendly as troubleshooting an incorrectly configured (permission) JIRA instance can be a hassle.
Sometimes when new versions are introduced, some of the older features are dumbed down to make it easier for the user but for power users, this could cause confusion if they were wired to do some tasks using the old methods.

Jira has a weekly release schedule which means the product is always being improved or changed. This is usually a good thing, although I will admit that sometimes it isn't. Jira is also incredibly functional for a broad range of use cases, from managing a simple to-do list, team task tracking, process automation, to software development. They do a good job of making it user friendly and easy to onboard, especially since they started making drastic UI improvements a little over a year ago.

A consequence of being capable of so much is that it can be hard to configure initially. More specifically, which features you need and which can be disabled. There are a lot of great features but some just complicate the workflow, and it usually takes time to figure this out.

1. Great User Interface and User Experience.
2. The ability to create custom queues and automatically re-direct issues to these queues saves a lot of time. 3. The inbuilt SLA management and the option of integrating it to third party alert and notification software is impressive.
4. Adding attachment, links and other resources to JIRA ticket is easy and straightforward.
5. It has great audit trail tracking and can act as a source of truth for all parties involved.

1. The issue search feature could have been a little more customizable and faster.
2. The options available to format the comments on an issue are limited and not very intuitive.

So far, the gold standard in project and process management, especially in the number of options, features, automations, integrations and workflows that the software is capable of handling. We shifted to this software when the pandemic hit and were forced to stay at home since we needed a more powerful software to handle our workflow. If you have a techy team, nothing else compares.

Biggest con really is that it is not the most user friendly software. Unlike Trello or Asana where you can just go fire it up and it's good to go. This one takes a lot of set-up to do and a deep familiarity with how it works under the hood. Given that the software is one of the older ones, you can sort of see it's age in both the older workflows (issues, screens, etc) vs the newer templates. The newer project templates sort of partially solved this problem but if you need to tweak the settings, it still has a steeper learning curve.

The con really here is that i tried Jira with my other less techy company (a school) and adoption was really low as users just weren't able to keep up with it.