Jira Reviews

Pros

I could tailor it to fit my team's workflow perfectly. This flexibility made managing projects much more efficient and organized.

Cons

As a new user, navigating through its numerous features and settings felt overwhelming. It took me a while to get the hang of it, which slowed down my initial productivity.

Pros

Good connectivity between items (epics, user stories, and so on).
Overall, it serves the basic needs of R&D management and collaboration with products.

Cons

Comnersum, many simple activities have bad UX and are hard to use quickly. The filters are not intuitive, and the navigation between different screens is not apparent.
The UI looks old.
Lack of many capabilities that would make product managers' work easier.

Pros

Integration with my entire team is a plus. Because all members can be in the loop

Cons

Kira is not user friendly. When you do the onboarding you need to pay attention to features’ location because the interface is confusing and it’s not easy to find what you’re looking for in a single glance.

Pros

You get the best ROI for using their service

Cons

Integrating is seamless
They have various external apps
Support is great

Alternatives Considered

ServiceNow Customer Service Management and ManageEngine ServiceDesk Plus

Reasons for Choosing Jira

Jira has plethora of things under one umbrella that let you manage everything from one platform.

Switched From

ServiceNow Customer Service Management

Reasons for Switching to Jira

Cost effective, it also has great customer support.

Pros

I like that despite is a big team or small team, it has a lot of features that help tracking the work, and with little customization you are ready to go

Cons

Sometimes por the product managers is a bit complicated to do things the right way, but I would say is more like they didn't investigate the tool more than a jira fault

Pros

Jira’s flexibility and customization options are fantastic. It really allows our team to tailor the workflow to fit our specific needs, making project management and tracking super efficient.

Cons

The learning curve is pretty steep. It takes a while to get the hang of all its features, and new users/employees might find it overwhelming at first. They reported this as well.

Alternatives Considered

Trello and Asana

Reasons for Switching to Jira

We chose Jira because of its advanced features and the level of customization it offers. Despite its complexity, the depth of control it provides was a game-changer for our larger projects.

Pros

Jira facilitates team collaboration by allowing us to prioritize projects and issues, track time spent on them, and use the comments area. Dashboards provide a high-level understanding of the project's status. Different statuses, such as new, resolved, testing, and fixing, are displayed to indicate the current stage of the issue.

Cons

From my experience, I noticed that the fundamental UI/data structure is slow and lacks context. It is slow to use and has low acceptance rates across the workforce.
Supervisors may log items in the system but continue to run Google Doc spreadsheets for tracking in parallel, resulting in data fragmentation. That, to me, proves that it is unsuitable a little for the purpose we need it for.

Pros

Its backlog feature really makes it easy to plan sprints.

Cons

The onboarding experience wasn't great. It could take some time to get familiar with all its powerful features.

Pros

I love Jira's flexibility and ability to manage multiple workflows within the IT service desk functionality

Cons

With the multiple workflows, you can be lost and not know which teams to route your request to but I believe this can be overcome by managing efficiently tasks and roles within the IT service desk function

Pros

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.

Cons

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!

Pros

The best part about JIRA is how visual the UI is. It is incredibly easy to track down and track through different tasks and sprints without having the hassle of digging through a 90s-style ticket system. My other absolute favorite thing about JIRA is the simple ability to tag individual users basically anywhere. This saves an incredible amount of time due to the way in which notifications are handled in and outside of the system. Collaboration is beyond easy with JIRA.

Cons

Many of the most important features are being deprecated over time, and the customer service component of the software seems ineffective at best. Some of the best features have been removed and the highest priorities on their roadmap aren't those that would severely increase users' quality of life. I think this is part of a growing process that the company is going through, but it does cause some heartache on the regular to think that our business desires aren't being met - even through months of users requesting the simplest of features.

Alternatives Considered

Redmine and Trello

Switched From

Redmine and Trello

Reasons for Switching to Jira

JIRA had a much more robust interface than the other options we were looking into, and overall it was the visual aspects of JIRA that won out over the others.

Pros

Agile development on Jira is great. The ecosystem allows me to track my time, organize my issues into tasks and sub-tasks, track when things get done, create estimates, and organize complex projects into smaller and simpler pieces.

Cons

The support is pretty ignorant of their user-base on several issues and refuse to add new features that would benefit hundreds, if not thousands. It can be very tricky to migrate, update, or set up. Plugins can cost money and it can add up, though I haven't spent too much at all for the value I received.

Alternatives Considered

Trello

Reasons for Choosing Jira

My prior employer used Asana but I found JIRA to be a better solution for an Agile workflow.

Switched From

Asana

Reasons for Switching to Jira

Trello is a watered-down version of JIRA and doesn't feature all of the technical details that JIRA has.

Pros

Of course there's a little confirmational bias in any review of a product already acquired, but implementing it really was a thoughtful decision. Over the last few years, this product has really matured. When we started with it as an immature FOSS offering, it wasn't really enterprise-class. We were motivated by cost initially, but Atlassian has really grown it. Now with external directory integration, tiered hosting offerings, MSP-level features, and significant customization available, I can't think of another product that beats the value proposition. My most favorite feature? The return on investment. We use this to manage service desk interactions with more than 25 MSP clients, and have never been let down. It costs us less than weekly staff meeting pizza to operate and integration with other Atlassian products is superb.

Cons

Much of the branding customizations fall flat. Inability to resize or edit logos, the prominently featured plugs for Atlassian throughout the UI, and clunky DNS-tricks requires to redirect customer portal URLs to MSP's domain.

Alternatives Considered

ManageEngine ServiceDesk Plus, SolarWinds Service Desk and ServiceNow Problem Management

Reasons for Switching to Jira

Cost versus features and ease of implementation

Pros

Coming on board with Delta I hadn't user the JIRA platform outside of submitting tickets in my past. There was a shell created by our IT team and it was a great start but with the help of an intern he and I were able to completely change and enhance the user experience on both sides for those who enter tickets and those who work or engage with tickets.

The system seems a little overwhelming at first because it offers so many variations however once you really consider what you want to do and who you want to achieve it really straightforward.
You're able to change and modify just about every aspect of the interface so that its complete company-specific or even department-specific is you choose. You can make it look like its an extension of your companies actual website.
You can access and run reports for so many different KPI's or metrics to see preformance or SLA's and they are all realtime.

Cons

Like I stated it was a bet overwhelming bacause there are so many options and changes that can be made using JIRA however there are tons of resources as well.

Alternatives Considered

Salesforce Sales Cloud

Reasons for Switching to Jira

We chose JIRA because it appeared to be the best application for what we needed. It was also expandable and we could scale it as needed in the future. We also like that it was completly customizable.

Pros

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.

Cons

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.

Alternatives Considered

Salesforce Sales Cloud, Asana and HubSpot CRM

Reasons for Choosing Jira

Salesforce was not suitable for our requirement and the type of business that we are doing. So, we have shifted to Jira and it's a very important decision for us to collaborate our exciting team.

Switched From

Salesforce Sales Cloud

Reasons for Switching to Jira

Jira is developer friendly, easy to work with, easy to collaborate with multiple people on the same task, have features to same attachments and issue tracking with notifications is very helpful to complete tasks on time.

Pros

a complete and very user-friendly workflow management tool that allows you to optimize work times with a perfect management of all tasks, collaborators, project delivery times and more generally "who does what" on each single activity. Thanks to the easy connection with Trello it is possible to have a complete and easily accessible platform also from mobile for the management of team work. once discovered you will not be able to do without it because it has a free version available complete with all the features you need to manage even complex projects.

Cons

I have been using this software for several years and I have never encountered a problem either at a technical level or at the interface with the different businesses that I have managed. Implementations are always welcome so I look forward to testing some new features that they will release in the future for now everything works great.

Alternatives Considered

Fullstory and Trello

Reasons for Switching to Jira

It is a complete and easy to use tool in a team, especially with creatives and developers. Sometimes I integrate it with the use of other software that may already be used in agencies or private individuals.

Pros

First of all, the tool is extremely lightweight from a deployment perspective and also from usability perspective as well. It allows for seamless saving of information as you type and that's a pretty good feature the user interface is very well laid out and is very easy to navigate through the tool across various screens. Teams across the organisation can view the status of the development items across different projects and across different boards, per developer. JIRA can also be used to track tasks and banwidth allocation for various teams as well. The extension of confluence is the best feature that you could extend to a JIRA instance for your developers

Cons

The amount of integrations that JIRA comes out of the box with can overwhelm new users. It does have a slight steep learning curve, but once the user is comfortable using the system they should be able to navigate through the tool seriously

Alternatives Considered

Zoho BugTracker and Zendesk Suite

Reasons for Choosing Jira

It was an organization decision to move to the defacto standard for task and issue management. The integrations that come with JIRA made it a no-brainer decision for our organisation

Switched From

Bugzilla

Pros

JIRA is a project management platform that definitely increases visibility and promotes collaboration, with multidisciplinary and even multicultural work teams. Jira organizes the planning and execution of almost any type of project extremely quickly, from large or large, where multiple tasks are supervised, and with a high degree of complexity, to flexible implementations that require simple and collaborative work.In this way, with JIRA we manage the entire execution cycle and even subsequent phases associated with evolutionary maintenance, roadmap, and support.

Cons

Jira is really intuitive, and its functionalities allow the successful execution of large or small projects, however, for the result to be impeccable, we must prepare all the team members and train them properly, and in this way we can expect a process without complications, on the other hand, the licensing may not be as flexible as other usable tools currently on the market but it remains in the average range.

Pros

JIRA is an industry standard tool, due to this it's very well known and a colloquial metaphor for "tickets" in and of itself. JIRA is able to handle monolithic projects and the many related projects with regard to them.
JIRA is very good at allowing and automatically building self-referencing tickets within it's comments and ticket parts, if you put a ticket title into a ticket it will automatically reference the actual ticket with a link. It is also very good at adding to existing tickets with related tasks, sub-tasks, and prioritization. JIRA also is considered in almost every third party tool with a massive volume of software that offers "JIRA plugins" considering it's high stature with the IT community.

Cons

JIRA is "the tool" but it's not "a good tool" for every project and company size. JIRA is like other commercial grade products that just aren't designed for simple day to day use. While it opens up nicely and begins to make tons of sense in larger projects, larger organizations, and larger teams it often doesn't show the same beauty with simple projects and day to day ticket tracking.

Additionally, the JQL language is ridiculous follows in the foot steps of many other proprietary languages that are only great for constant users of JIRA. While that's the implied scenario because as mentioned JIRA is "the tool" it's not always the case. When my day is split 20 ways, I have little time to sit down and do more than plug in a JIRA ticket number to get to the issue to investigate, review, get sign off on a fix, and apply.

JIRA is also having what appears to be a lot of difficulties this year staying online with their new data center providers. I don't remember ever having these issues prior to their most recent move.

Pros

Jira is the great tool when comes to administratering the custom workflows. We were able to define and automate most of the workflows tasks thus reducing lots repetitive manual efforts. As an administration, we have so much of knowledge base available from Attlassian. Out of the box, we get generic yet useful workflows and features which can onboard most of the software and agile projects instantly.

Cons

Able to import and export workflows from one instance to another Jira instance is missing.

Alternatives Considered

ServiceNow Customer Service Management

Reasons for Choosing Jira

More user-friendly tool

Switched From

ServiceNow Customer Service Management

Reasons for Switching to Jira

Cost and ease of use

Pros

Pro 1: Easy Time Tracking
One of my favorite things about Jira is its time-tracking feature. You can easily track which team members spent their time working on certain issues, giving you insight into how your projects are progressing. (This could also be a con if you work in a more collaborative environment).

Pro 2: Easy Project Management
Prioritizing tasks is an essential aspect of project management. With its dashboards, Jira allows you to prioritize projects by quickly identifying which are progressing well and which need help. With a quick glance at your dashboard, you can easily prioritize what’s next for your project teams.

Cons

Con 1: Technical Issues
Projects created in Jira have an issue type called technical that is often confused with bugs. Because issue types are pre-defined by default, it’s hard to use your own words to describe what a technical issue is. When you create an issue for a bug or technical problem, there’s no way to group it with other issues about similar problems so users can focus on problems across several projects at once.

Con 2: Difficult to Get Support
The biggest negative about JIRA is that it's tough to get support when you need it. This is due to Atlassian's heavy reliance on their community forums, which are frequently inundated with low-quality questions from new users. If you have a complicated issue, or your problem isn't being addressed in any forum threads, Atlassian's usually helpful but small team of professional service agents (PSAs) may be a better bet than waiting for help from other users.

Pros

Jira provides a ton of features in terms of project planning, the ability to create a hierarchy of epics, and feature > delivery > story, which is a great feature to track deliverables in a release. It provides sufficient options to write detailed stories, add functional workflows, excel data sets, etc. Helps in Issue and bug tracking during production support, UAT phase, and QA testing. A great collaboration platform, due to the ability to write comments, notifications, tag required personnel, and seamless integration with other tools such as Outlook and Confluence.Log efforts and Tempo (dashboard to track daily efforts) is an amazing tool for productivity enhancements.

Cons

There are a few limitations of JIRA as well - - The search engine of JIRA doesn't always fetch the correct results despite using the correct keywords, it's not as smart as an AI-powered engine or Google. Also, the Smart Query feature is not that useful, many times basic search work well.- Doesn't have the templates to write detailed documents such as FSD or a design document, not a very good knowledge management tool.

Pros

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.

Cons

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.

Pros

I love Jira because of the Atlassian ecosystem. Our Product Management team lives out of Jira for our day-to-day task management, and we work in a 2-week Scrum style. We use Confluence for our documentation and product requirement documents, then Jira Product Discovery for road mapping, prioritization and idea tracking. All products in the Atlassian ecosystem work seamlessly together.

Jira gets a lot of hate for being complicated and hard to implement, but like many things, its biggest strength is also its biggest weakness. I love Jira because its flexibility means it's a tool that our whole company uses, from Development to Customer Support to Product Management. This makes it easy to collaborate with other teams, without having to jump between and learn other platforms. Having a couple of people in the company who know Jira inside out mitigates any implementation challenges some may complain about.

Cons

I despise that Jira third-party tools/addons are billed by the number of active Jira users you have. This means that if you want to use an addon for a small team of 5 users, but you have 100 Jira users, you have to pay for 100 licenses. This billing model makes no sense and means it is financially not feasible to use most addons, which our teams could greatly benefit from using

Pros

Jira is a task administration programming that is very mainstream among numerous organizations. With an extremely high score of 9.4/10 and client fulfillment at 99% it is as of now one of the best 3 best task administration arrangements looked into on our site. The primary spot in this class is held by Wrike which has an aggregate score of 9.8/10 and is the champ of our Best Project Management Software Award for 2017. You can experiment with Wrike for nothing here. You can likewise contrast Jira and Wrike and see which one is better for your organization.

Jira is intended to enable clients to catch, dole out, and set needs to their work. It enables you to deal with the entire procedure of use improvement ensuring that everything is secured, from idea to dispatch. Its straightforward, natural interface empowers joint effort with partners and enables you to take care of business in a viable way.

Jira tailors itself to fit to the necessities of the business and gives fantastic help to finish everything. The level of customization enables the product to properly fit distinctive business needs.

This product can be utilized by an organization. I have designed JIRA to be utilized by distributing organization, by law office, and obviously, IT organizations. What's more, it was conceivable to make everybody content with what JIRA gives. Despite the fact that occasionally it was difficult to encourage individuals how to utilize it, following multi month or two they couldn't recollect how they lived without it.

Cons

Jira is an amazing programming, however with a lot of capacities comes a large group of devices and assignments to learn, especially for new clients.

As of late JIRA refreshed its outline. My clients whine about new outline, I get insane when I can't discover things. Furthermore, JIRA wouldn't like to stop at that and is refreshing its plan further and further. I would truly incline toward that they glance through bugs that were raised on comunity entryway and accomplish something in regards to new highlights as opposed to doing configuration refreshes.

It is imperative to realize that Jira gives us awesome help to the client, and their consideration is a need, however ordinarily they don't figure the issue. It is a component to survey in Atlassian.

- The prologue to Jira's reality is required to be as mysterious as its interface and execution. Actually it is intricate to fabricate channels and move around in the application when the client is new.

- You need to run a right download of the reports toward the finish of the month or toward the finish of the week, the reports are conveyed in spreadsheets, however with an introduction that fails to impress anyone, thusly, when setting the dates they ought to have pretty much days so you can play out the download effectively.