Jira reviews

Het fijne aan de software is dat je een prima overzicht hebt van de taken die er aan jouw profiel hangen. Je kunt hierdoor makkelijk prioriteiten stellen. Daarnaast is het fijn dat je met meerdere tegelijkertijd in een project kunt werken en altijd de laatste bestanden kunt gebruiken zodat iedereen altijd met hetzelfde bestand kan werken.

Het dashboard op de homepage komt wel wat rommelig over. Je moet goed kijken wat er in welke kolom staat.

I absolutely love Jira—it makes project management a breeze! The @mentions keep everyone informed, the API integrates smoothly with my other tools, and the access controls keep everything secure. The activity dashboard, tracking, and reporting features are fantastic for staying on top of progress, while the Agile methodologies and alerts ensure I can manage workflows and stay updated effortlessly.

I found that the interface can feel a bit overwhelming for new users, and it took me some time to get fully comfortable with all its features. However, once I got the hang of it, Jira became incredibly powerful and efficient!

Features such as Scrum boards, kanban board, sprints, and backlogs are great for teams who follow agile methodology. We can customize workflows, fields, and issue types as per our needs. Most important feature is that it enables us to track the project progress in realtime. In addition, it is compatible with many external apps and facilitate the smooth workflow.

Extensive features and customization options can make the initial setup complex, especially for newcomers to project management tools. Its lacks built-in idea management functionality, we need to use some additional tools for brainstorming and concept development. Also, the pricing seems to be bit high and it may not be an affordable option for small teams or startups with limited budgets.

Customizable workflows , where the tool can be customized based on the project type and needs like agile and scrum.
Powerful issue tracking, where you can track the project issues and you have dashboards to monitor and prioritize
Multiple plugin options

Though , it is an issue tracking tool , i doesn't have an inbuilt testing toll feature. We need to integrate this with third party tools for testing.
Availability of lot of plugins are creating chances to over doing the info and makes it complex

Jira streamlines workflows with automation, while providing in-depth reporting on project performance.

It perfectly meets our needs and I have no complaints.

The biggest strength that Jira has to offer is how customisable the app is. We're forever fine tuning how how development flows are setup and I've never run into an issue where what we wanted to achieve could not be possible. The workflow editor is pretty straight forward once you figure out how to map these to specific projects and features.

It also has a mammoth number of apps that can integrate with it, which can greatly help simplify your organisations stack. We use a bunch of apps that connect to Jira such as Slack and Git.

The mobile app is pretty good and more simple to use. There's also a new iOS app that you can run on a mac that seems to be a slightly faster and more user friendly version. However, I haven't quite worked out how to tailor the notifications.

The search is very powerful!

It is very slow to load pages and jump between stories. When using this on a daily basis it really gets annoying.

When we need to change a setting it's hard to work out where to go. I have to say I've never seen another app quite like Jira which has so many different places to go to in order to change very similar settings.

If someone accidentally creates a ticket with the wrong type the only way to change it is to Move the ticket. And I can't seem to change the status of the ticket at the same time. So often an Open bug ticket becomes an Open feature ticket, which really should still be in Draft.

We use JIRA online and it's dead simple to create and manage complex tasks. I love the ability to integrate with great packages like Confluence (which is SOOOO much better than Slack!).

Getting new employees up to speed on using the software is more time consuming that it should be. I'd prefer a more intuitive UI.

If you are looking for a management system that is good enough to cover all your needs then Jira and the Atlassian portfolio is exactly what you are looking for. Every aspect of your workflow is infinitely customizable and perfectly integrated with their entire suite of software development tools. Once your setup is complete everything is easy and automatic for your team. The potential for boosted productivity is huge.

All the updates can be overwhelming. Great updates can provide users with additional features without affecting present ones but some updates are breaking and requiring you to find the relocated setting in order to configure what you want. That is adding to the already high cost of setting up a new project. If you have someone dedicated to administration then the rest of the team will have a great experience. This is a very powerful tool and that means it will take time to learn and properly manage it.

The service which is the Cloud version is just as you would expect from the Helpdesk Type system. You have the ability to manage permissions to what access users have. You have plenty of third-party integration options. Also, one of the most important services is the ability to integrate Azure SSO.

One of my pet hates with this service is the tickets themselves in that on some tickets their comments can get lost in that the system starts to hide the older comments so if you are in a rush to get some info you need to unhide those comments

Jira allows us to efficiently manage a tasks across a wide variety of different projects, assigning work easily to each team member and allowing us to run a clear process from briefing through quality checking. It has allowed the team to communicate more effectively and improved the overall quality of delivery with better expectation management.

We've used a variety of different task and process managment tools in the past - and still do for direct client work where they have a preference (e.g. Basecamp, Asana etc), and the interface on Jira is maybe not as attractive, but it works fine and allows good interaction.

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.

If you are willing to do the work, the advanced search is useful and the user experience isn't bad except that to eliminate done tickets you have to deselect all then re-select every option except those of a done type.

Advanced search is the only useful way to reliably get information out, making getting even the smallest view of your data onerous. The core advantage of the tool - it's lack of structure - make it difficult to complete even the simplest of tasks without a ridiculous amount of effort. It's biggest failing is that everything is too flat by default. For example, I am working on a project now and the team has made duplicate tickets because the original tickets are too hard to find and are just dumped on the screen... we have sometimes used epics/stories/sub-tasks with sprints but these are truly inadequate... in today's time why should someone have to spend 20-30 hours a week grooming the backlog and writing searches when if the tool was any good it should (!!) be able generate these views automatically. We are now investigating other solutions like Wrike (absolutely no affiliation, not even sure we will switch to it) and in 10 minutes of testing we were getting views that we have been struggling to get out of JIRA for over a year. Also, you can't do something obvious like make a reminder in the future for a ticket, so you either get flooded with reminders for just about everything or you have to go outside the product to remind you to do something in JIRA. Seriously!?!

Couple of features below that I really admired the most-Mobile version of Jira board, colorful status tracking with accurate percentage, effective customized workflow modal, quick peek view of tasks in dashboard, search option for any filter, quick catch for getting user by using '@', easy query handling and filters, easier mode of cloning tasks, linking items and referencing, multiple built in report types like bar chart, pie charts, etc., Kanban & Agile flexi boards, vast of plugin support like git-hub, git bucket, zendesk, etc., From the admin point - easy configuration of development tools dotnet, configuring mailing options, deep level view of audit logs, watch list for issues.Couple of features below that I really admired the most-Mobile version of Jira board, colorful status tracking with accurate percentage, effective customized workflow modal, quick peek view of tasks in dashboard, search option for any filter, quick catch for getting user by using '@', easy query handling and filters, easier mode of cloning tasks, linking items and referencing, multiple built in report types like bar chart, pie charts, etc., Kanban & Agile flexi boards, vast of plugin support like git-hub, git bucket, zendesk, etc., From the admin point - easy configuration of development tools dotnet, configuring mailing options, deep level view of audit logs, watch list for issues.

Sometimes I feel, the JIRA GUI is clumsy to have many things in dashboard, other than that I do not see any specific negative factors to hate JIRA, and it depends on how we use the features for projects.

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.

Jira is *incredibly* versatile. You can customize almost every aspect of your Cloud instance, Project, Boards, & Workflows to fit nearly any use case, and across multiple departments.
Permissions to your Jira instance can be restricted at a very granular level if need-be, but can be more broad if the occasion calls for it.
Additionally, and probably the largest reason we transitioned from enterprise Jira to a Cloud Jira instance is the pervasive availability of integration across the market.
Speaking of market - Jira has a growing 3rd-party market that offers enhancements to the Jira platform that Jira does not natively provide or are too complex for an untrained Jira administrator to script themselves. Of those that are "approved" by Jira, we are extremely happy with the breadth of functionality, integration and ease of use.
With all that I do have to say that our favorite thing with all project leads is Jira Automation. Once you understand the "SmartValues" language that automation runs on, the use cases for automation are truly endless. It is one of the many strong features from a project management perspective.

Jira takes a village. Atlassian has an incredible resources in the "Atlassian Community" and they do a great job of having experienced users there to answer questions but, because each instance can be set up so differently, the actual customer support request portal is limited to bug fixes. As a result, much of my time administering Jira is spent researching how to fix a roadblock or how to modify permissions - a lot of "learning by doing". Generally speaking, Jira can be difficult to use from an administration perspective, *but* for the purposes of moving ticket along, the UX is pretty good and the UI is fairly intuitive.

I use Jira at work everyday. It helps me organize my tasks, keep track of my progress, and connect with my team more efficiently. Jira allows me to customize my workflow, issues, and fields to fit my unique needs. This flexibility helps me to avoid confusions, and improve my productivity.Furthermore, Jira integrates with more than a thousand third-party tools, such as GitHub and Slack. This integration capability is very important because it facilitates cross-functional communications.Jira's reporting features are very essential. It allows me to monitor my progress, identify bottlenecks, and make data-driven decisions. The reports can be customized and exported in various formats.Jira helps me to prioritize work, and deliver value faster. I totally recommend project managers and company employees to use Jira at work. It helps you be more productive at work.

In my opinion, there are no cons for Jira. The only thing I can mention is that the software can be overwhelming for new users due to its rich features and complex interface. It requires some training and patience to fully utilize its capabilities. However, I do not consider this as a dislike. It is a faily user-frienly software. I enjoy using Jira at work!

This tool works on a hosted model and can be accessed from anywhere in the world by using internet connection. The web version and even the mobile version (which i guess has been recently launched) is good and can be accessed through click of a button while it is assigned to you. It is has various options like assigning to different users, obtaining their comments, attaching supporting documents, printing the ticket, reports and dashboards which can be customised by the users, option to download, link the ticket with other tickets, etc., The tool has the option to create various workflows as per the requirements of the users. It has the option to alert the users with email alerts and also reminder mails. There is option to close the ticket, clone the ticket, revoke the ticket. The users can customize the reports and dashboards as per their requirement and download the ticket in various formats from the JIRA tool.

The reports and dashboards does not provide for reports in a graphical way. The tickets can not be simultaneously assigned two or more users. The tickets can only be closed by the creator which is a set back if the creator does not close the ticket once its gets over. The note which is created allows only text inputs. It does not allow for creation of table or column. Turn around time for closure (at each specific user level) of the ticket can not be generated from the reports automatically. This is a big drawback. Also, it takes so much time for loading the contents and if the internet is slow then it does not get loaded at all.