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.

We used several bug tracking tools in the past but Jira is by far the best one. What I like most:
- user friendly interface, provides a nice user experience
- Agile SCRUM/Kanban support out of the box
- extremely configurable on almost everything
- extendable through custom scripting, either built-in or via addons
- very collaborative
- there are thousands of addons in the marketplace; you can even write your own

Being so flexible to be configured, the learning curve for admins is a little steep.
The price is based on the number of users and if you experience wide user adoption in a big company, you end up in paying more for upgrading to the next tier, than if you would pay for that tier first time.

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.

*Functionality

The best feature of Jira is a huge number of integrations, massive amount of possibilities, statistics and tricks that you can you inside the platform.
There is an integrated tracking, kanbans, lists, sorting direct contact with chat (stride) and feature to work with git right from every task or issue.

* New UI

Recently Jira got an update, a new chat (Stride, instead of Hipchat) and a new UI for the tasks. I can see that company goes in the right direction to adopt all of it's powers.

*Customization

Jira, being confusing at first hides a lot of it's features inside most of which you can change and adjust to your business needs. It is a great solution for a big corporation with dozens of departments, hundreds of employees and thousands of issues and tasks daily. However, in all other cases Jira can be a nightmare at this point.

*Slow

Out off all CRM platforms and tools to handle tasks and issues Jira is the slowest by far. Is it initial problem or has it appeared after adopting so many technologies under one roof - I can't be sure. But one thing is clear - Jira is awfully slow.

*To many features

Yes, it is a disadvantage when it comes to Jira. When a new customer comes to Jira I believe, he is most definitely confused. Especially, if he/she tried ANYTHING else before. Of course, I see that company does a lot to make it easier and more comfortable, but as it is now, Jira is a terrible solution for fast adoption, scary for a small or middle sized team and most definitely not a great choice for personal use.

Jira is Huge. If you are huge - great features, customizing, different apps and plugins will help you solve a lot with Jira. If you are just starting or don't have that many tasks and issues and people in your company - you should probable check other options.

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 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.

I like the most the integrations available (Bitbucket, Slack, etc) and how customizable the software is. You can define which detail to include in any new created task, project, etc.

I liked least the format used for uploading files. With this purpose Jira works together with conduent in a "Pages" format but I would prefer a File Management System based on folders.

I've been on teams that have used Jira for more than a decade now. Now I manage teams that use it and we certainly get a lot of value out of it. I love the power and infinite flexibility to customize everything to our needs. It's incredibly powerful, fast, stable, and powers all of our cloud, app and firmware deployments/releases by managing the user stories and bugs that go into each release.

The user interface is now so complex that we have to employ full time people just to wrangle Jira. The PMs themselves are pretty scared of it and would never try to customize it--the TPMs and Sr. TPMs often struggle to do what we need. It can really take on a life of its own because it's so incredibly complex. We have had to move a lot of project management tasks over to Asana because there are so many things messed up and broken about our current Jira (cloud) instance. Bottom line--don't choose Jira unless you've got SDEs that are super adept at it already. If you're just starting out, it's very attractive pricing, but the complexity will kill you. Go with something easier.

It does its job pretty well and that's why it's been used by most enterprise companies. The ability of tracking and sprint planning is very good. I also liked the way it manages the coordination between different teams. It's always very simple to create a JIRA, assign it to the team members and get the task done.

UX could be improved a lot. Most of the time I had to use Google Sheet to manage my tasks with JIRA ID. It's mainly because of the complicated UX to manage the product roadmap.

Workflow customisation is by far the best of any software that i used. Also connecting confluence pages with jira tickets helps a lot for better documentation.

Sometimes it is slow or wont load. Also i have a felling that the state of a ticket changes on its own, but not always.

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.

1. Different user roles can be defined to allow for segregation of duties.
2. Epics can be defined to assist with long and intermediate project planning.
3. Duration of sprints can be defined according to project requirements.
4. Statuses for user stories can be used for tracking progress as well as workflow management.
5. Allows for bulk import of epics and user stories which can fast track administrative tasks where this information has been captured elsewhere e.g. CSV format

1. Only users from within the organization can be assigned to tasks and user stories. This can cause unnecessary delays where external users need to provide urgent input or contribution.
2. Statuses (user stories) cannot be defined specifically for a board where multiple boards exist within a project.
3. Only two types of users can be assigned to user stories, which are assignees and reporters. JIRA does not allow for multiple users (assignees) to be assigned to one user story.

I like the kanban board, it works very well and looks simple to use (but it's not easy to setup). The task management for business project is very nice and the new feature of being able to look at the overall work like in a spreadsheet, definitely beats Smartsheet for me. I like that you can easily move your work when you're done using the board view, if you like.

Scrum/Agile can be difficult to setup because the Kanban board isn't so great when setting it up. I have run into some difficulties with it, their support board was helpful but it did not resolve the issue.

Business projects do not have the ability to link to Bitbucket, it would have been nice to include task management with Bitbucket integration, it helps to appropriately follow up on tasks.

The board view for tasks and sub-tasks doesn't work for me. I'd like to see that there are major tasks with steps of the child tasks (change the subtask icon too).

JIRA is one of the best, simple, and user friendly project management tool. We have been working for almost 3 years now and the user experience it offers is applaudable. You can create your agile boards for scrums and can go KANBAN as well. You can create as many different teams and squads. Link your issues to stories and trace it to the feature, Track how much effort is being spent on an item; Track for how long an item has been been sitting idle; Prioritize your issues, backlogs; Create dashboards for ease and convenience; generate reports, traceability matrix, velocity burndown charts; add/remove user access. You can customize it as per requirement and with ease. Recently it has moved to cloud, so down time has been relevantly decreased which is an added bonus. Best part I like about using JIRA is that its very easy to handle, we can do bulk update on items and it takes very less time to understand. This is one of the best tools that is out there and I believe almost every organization is using it.

There is nothing much to add in this section. Practically I am all thumbs up for JIRA. I have a suggestion though. JIRA needs to have a Instant Messaging option enabled so that an organizations do not need to look out for a separate tool. I think if Atlassian would be able to achieve it, not only they would be able to enhance their customer base but they would be able bring a lot revenue.

It's a very powerful tool. It provides many advanced features to collaborate with people. We can easily tracks things on Jira through our mobile devises and other gadgets. It helps us to plan the projects with tasks and sub-tasks.

It is an expensive software compared to other open source software. I have worked with many software Jira is one of the most expensive product that we have used in our projects.

Jira is excellent at keeping track of our issues and linking between them on a kanban board. It was our introduction to a Kanban system of tickets. There are also many features we see ourselves using that we are on the verge of delving into, allowing us to focus on the tickets now but expand in the near future.

I like that tickets are easily linked to each other. Our previous system made it difficult to know which tickets were related, while Jira has several options for relating tickets (related to, duplicates, blocked / blocks/ etc)

I think the price can get high depending on how big your team is. We were just over the free limit which becomes a large cost, especially once you include subscriptions to confluence etc.

I think the load times and UI can get buggy at times, there are multiple times a day I have to click through menus several times for it to register. This is by far the most frustrating thing, especially when you have many tickets on a page.

One issue we had was that our current ticket system allows us to CC users onto tickets so they (+ anyone else we add) can get an update. This was not possible through regular Jira, however something similar could be done with effort on the Jira Service Management side.

It's arguably the best software I've used for project management in my team, it's quite efficient, has some cool features like linking your tasks to a git branch repository, it's generally a cool software to use in an agile team.

It can sometime be complex navigating around and may need some getting used to. Sometimes needs refreshes in order to check for latest changes in a sprint or during a backlog grooming session.

* Allows the issue flow to be perfectly configured to match your software development practices.
* Highly customizable process management - define the properties of issues and how they transition between states.
* Integration with many other products, like Slack & GitLab

* "Next Gen" project type lacks many features of Classic projects.
* Classic Project configuration is full of bloated features and complexity
* Next Gen projects sometimes have frustrating bugs and limitations that don't get fixed for years.
* Issue transition between Next Gen and Classic projects is not smooth (custom properties don't carry over)

The ability to manage tickets day to day was a must. Some of these were coming from external parties and others internally. We ended up using it across the company in many departments so the ability to have multiple projects was a must.

Cloud version support for plugins and customisation is limited to only the basics. Its not possible with dive in to it inner workings and develop your own without tapping the APIs externally.

This software is so great, that you really don't need to train people on how to use it. Project managers will be familiar within a day, and users will understand it quickly because Atlassian put a lot of work into an intuitive user interface.

This is the best option on the market if you want something that scales across your company without draining your energy. Not only will you run projects through here, but you can also setup all your standard business processes to run through here.

Using the marketplace, there are some great extensions for Jira. We built our entire accounting team into Jira, and used it to know we were following through with our key daily, weekly, monthly processes. Using a scheduler plugin, we were able to create tasks, with subtasks, delegate them, follow up with progress, and print a custom summary report at month end outlining completion, completion date, user, and notes.

You will likely want confluence or google sheets to keep overall big picture notes.

My organisation uses Agile software development to do product development, it would be appropriate for me to say every one of us uses this software right from the developers, to QAs to designers to Product Managers to even the senior management. Everyone has their own work areas inside JIRA. It is difficult to say in few words what JIRA is, it is a complete suite for a software development company and I'd suggest you try out JIRA no matter the size of your team. My main work areas and familiarity are the backlog, story management and issue reporting. JIRA acts as the single source of truth with its easy to use Epic and Story feature which makes the life of a product owner very comfortable. The development teams are then able to do their story estimations and sprint planning all in the same place. I would highly recommend you to try JIRA even if you are a startup or a big software house.

JIRA has a learning curve (at least for me, coming from a non-technical or project management background) but with a bit of training (can be done by yourself) it is not that hard to get up and running. Initially, I struggled to find my way around the software and also didn't know how to use some features and tools. But when you get accustomed to the UI, you will realise the power of JIRA.

It is an outstanding platform easy to use, with a great UI design, and wide range of customization and con configuration.

It has standard templates to manage projects according to current approach and new trends (Agile/scrum/PMI). It service desk offer everything you may need to control all of the process internal and external.

It has a large number of app to aggregate, as well as REST full API, Webhooks, and the likes to extract data or make interfaces with company's systems.

About the cloud service, is a litther pricy, and most of the time you need to contract (monthly fee) some apps to do basic things.

On the other hand, support service has its opportunities. Response time is quite slow, and in some occasions -simply- not attended.

Jira is being adopted by more Development Teams within our organization and now we are able to use the SmartSheet integrator to report project metrics. This tool allows us to sync our task status to one or more sheets to manage separate deliverables as well as projects. It limits the need for Teams to report data in multiple applications.

While the integrator is useful, we cannot edit or view the details for workflows created by others. The integrator(s) have not worked well with Confluence, but that may be a training issue. I would also like to use the API if possible.

Tracking tasks is a time consuming effort, and one that is easy to forget. Luckily, there is Jira. Jira lets you track your tasks and time spent on them without encroaching on your day. It is easy to set up (once you know what you are doing), easy to use, and a delight to look at. It provides the time tracking and issue tracking tools that any serious project requires.

It is hard to set up the first time. You need to know which functions you need and which you should remove. But once you set it up and know how it works, it is a treat to work with it.