Jira Reviews

Jira is a one-of-a-kind task management system, it's long learning time is offset by its amazing functionalities

Comments: Jira is a one-of-a-kind task management system that, while complex and not the easiest to initially learn to how to use, offers features and capabilities that other similar products do not have anything similar to

Pros:

My software team can use any type of any type of developer environment, custom workflow designs, offers creative features I did not even know I would like and utilize, good value for cost

Cons:

Hard to learn how to use at first, not the easiest to communicate between users and administrators on the program

JIRA allows us to align the entire team in a single direction!

Comments: In general, I consider JIRA as a tool that after being adopted, we simply cannot stop using it. In addition to being very intuitive, coworkers can be informed or report the progress of activities from their mobile device.
It is excellent for involving all departments of the organization in a single direction, when we talk about executing a project with own, contracted or external resources.

Pros:

Jira is a very complete tool for tracking tasks, sharing work and, in general, for project control. Getting started with it was very simple and requires practically no learning curve. A very useful feature is that it can be adapted to almost any type of project and the use of templates makes it easier to adapt to the way we want to manage our resources. Notifications can be configured automatically or specifically for a person and we can share documents and photographs as evidence of our work.

Cons:

Its licensing may not be as flexible or accessible for small businesses. Therefore, it is important to consider the total number of licenses for which we must pay to use all the functionalities of the tool. It is important to understand that we are storing the historical memory of our projects and even many times contractually, we are obliged to keep this information available several years after finishing a project if the contract requires it.

Improves productivity, but misses a few basic features to make it even better

Comments: Overall, my experience is very positive. There are minor issues and things you have to work around, depending on the use case. I worked with Jira both as a user and an admin. There were minor issues affecting productivity with both, but it's definitely net-positive even for a smaller team of 2-3 devs.

Pros:

The standout features are the high level of customisability and the development integrations. I was able to set up automations based on our pipelines. We used Bitbucket from Atlassian as a version control system, so the integrations worked even better. I like that the platform is fairly friendly for smaller dev teams, too. While some features are price-locked behind higher tier plans, it's doable for small teams with lower budget, too. When you need extensions, that's also manageable because most of them are free or cheap under 10 users.

Cons:

I had two major problems. First on is that automations are very limited in executions on the lower tier plans. Actions like "assign on transition" should be a basic thing that's included in all plans, unlimited. Assigning tasks to the right person at the right time is crucial for lean operations. Second is that project duplication doesn't work very well. You lose some of the issue schemes, workflows, etc. At the same time, every time you create a new project, Jira creates new schemes/workflows for it - even if you use the same ones for all of your projects. That creates clutter, and to my knowledge it was impossible to set up a project template in Jira cloud. Other than that, at times, the interface can encounter bugs. That's understandable with the complexity of the product, but it's still annoying.

Good riddance

Comments: I've been a Jira admin almost all my professional career, and I cannot take it anymore.

Pros:

I like Jiras Query Language. It enabled users to dig deep into the data stored in Jira to retrieve just the right info.

Cons:

Jira has grown into a bloated, inconsistent hot mess. Atlassian earns money not just by selling Jira licences (with horrific pricing), but by not implementing state-of-the-art features. They let others do that and charge a marketplace fee.

Best at small scale delivery

Comments: Unmatched in capability and ease of use. Pricing structure makes it easy to make accessible to every business size. Integrations with online collaboration tools have made WFH seamlessly easy. People can overcomplicate how projects are built, so it needs at least one experienced or continuously curious employee to keep benefits > overhead.

Pros:

It’s highly customisable- can be as simple or as complex as you need (which means it will work for you and not you for it). Usually, with this though, come specialist roles that you need to hire for (e.g. ‘salesforce specialist), but jira has easily the most extensive publicly available knowledge base. Every question or issue you may ever have, someone has had (and solved) before. Excellent community that also ways has a step by step for you. Continuous intro of new functionality. Integrates with pretty much everything out there

Cons:

Not so great when required for large scale delivery. Planner tries to do this, but feels like it doesn’t have the same level of user insight as the rest of the atlassian suite.

Love Jira!

Comments: I really like Jira, it keeps everyone in the organization involved and accountable to their portion of work, and takes out the weight of trying to remember and write down everything that is needed from you. You can just login and refresh your mind!

Pros:

Jira makes it very easy to make sure no aspects of a project are overlooked or skipped when moving with speed within our organization! Every step is documented and visible, keeping organization throughout time sensitive projects!

Cons:

It took me a bit to understand the different dashboard views within Jira, jumping to see just my tasks, all projects I'm apart of, and kanban views. I know it well now, but I remember some initial frustrations with that when first learning the system

Jira is great for workflow management with technical teams

Comments: Overall we enjoy using Jira and it is a great product for use to use with our technical team.

Pros:

Jira really helps with workflow and completing projects on time by splitting the tasks into manageable sprints. I like that you can put tasks that are not urgent into the backlog so that you do not forget about them. It is also nice to be able to communicate on the platform directly on the tasks.

Cons:

I would like to be able to change some of the task codes after creating them but you are not able to change it from task, to story to bug unless you delete it and recreate it.

Effective but sometimes can be a little complex

Comments: Overall, Jira has been a great tool for managing our projects. Once you get used to it, the efficiency and organization it brings to the table are well worth the initial effort. It's a robust system that helps keep everything on track.

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.

The BEST Collaboration and Work Management Tool

Pros:

Easy setup, easy cross-team collaboration, easy to build and deploy automations for jira and 3rd party integrations.

Cons:

Different licenses across different products can impact your feature set for all products... it's a bit odd.

Alternatives Considered: Trello

Reasons for Switching to Jira: Feature set matched our needs, ability to run Sprints was critical for our team.

Superb experience with Jira

Comments: Very smooth experience . Using Jira is a breeze , The UI is amazing .

Pros:

Loved it since it provides all the bifurcation of technical issues in no time.

Cons:

There is nothing we dislike about it, except that it could be more interactive to provide a more personalized experience.

Finest application for the Agile software lifecycle

Comments: I use JIRA in all the Agile software development for classification and bug tracking for every user with Dashboards. I am satisfied with the JIRA features but I think JIRA needs to provide more integration towards CICD tools so that user can get more idea about the bug tracking.

Pros:

Easy to create Agile dashboards to track bugs in different development life cycle. We can also extract informations regarding the user specific tickets created and worked for any period of time. Also we can attache documents to gives an entire idea about the the bugs and time tracker in comment section provides how much time it takes to fix the bugs. In the software industry JIRA is one of the widely used Bug tracking platform. The idea of classification of tickets like EPIC,Task are very useful to identify the work load needed for that ticket.

Cons:

Need exact date and time of the ticket creation and comments when the ticket gets older, right now it describes like the ticket is "created more two weeks ago". JIRA also needs to integration with CICD tools for more information regarding the bug tracking and fixing. JIRA should provide a dashboard for each user how much time he worked on a ticket to track the overall work time and also it will be very easy for the Administrator also.

Alternatives Considered: Redmine

Reasons for Choosing Jira: Redmine lack Agile development life cycle features like an effective dashborad , exact classification of tasks and the work time logging.

Switched From: Redmine

Reasons for Switching to Jira: JIRA provided more features for the Agile development Lifecycle that suited our work environments and continues to give more features everyday.

JIRA is essential for good software development but you NEED to invest in configuration

Comments: I love JIRA because I am an organizer and I spend the time getting it right. But you need that kind of commitment for the best experience.

Pros:

The powerhouse controls that allow you to configure exactly the solution you need. JIRA is unmatched in customization. For controlling workflows, getting status updates and clearly understanding what's on your plate, JIRA is amazing.

Cons:

The use of JIRA without properly configuring it. Without that commitment, JIRA can be offputting and seem like a heavy mess of a system. You need to remove what you don't use, need to set everything up for individuals and you need to educate your team about how they can use the system. It's so open that it can overwhelm people without management.

Alternatives Considered: Bugzilla and Trello

Reasons for Choosing Jira: JIRA is more structured and better at reporting.

Switched From: Bugzilla

Reasons for Switching to Jira: A comprehensive solution, including the use of Confluence for doc management.

Review for Jira as a developer

Comments: We moved our IT department to start using Jira for the teams that work in development. We have not yet moved our Helpdesk or "system uptime" teams over since we are still looking at what product works best. So with the smaller team, I believe it has helped in keeping our tickets in order. It is simple to see what is currently being worked on in each project. We do not have the highest plan so we do not have all features, but I think our current feature set is large with room to evolve.

Pros:

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)

Cons:

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.

One of the greatest defect tracking and project management tools in the industry

Comments: Project and Time management in many cutomer projects

Pros:

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.

Cons:

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.

Alternatives Considered: Bugzilla

Reasons for Switching to Jira: JIRA is quite easy to migrate. Easy to train and educate the team in fastest time possible. Easy to handle the administrative tasks and correct when needed.

Jira can help you tremendously if user the "right" way, or you can shoot yourself in the foot

Comments: I really like it, as I can configure it to suit my needs, I'm constantly reviewing the testing process in our company, making changes to the workflow, adding custom fields, etc.

Pros:

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

Cons:

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.

Alternatives Considered: Trello, Azure DevOps Server and Asana

Reasons for Choosing Jira: Jira is the industry standard and it was more affordable at the time as well.

Switched From: Wrike

Reasons for Switching to Jira: There are a lot of people who know how to use it, both regular and advanced users.

I enjoy Jira software but there are few things that can be improved in my opinion.

Comments: My overall experience with Jira is good and I do not plan to switch to other tool right now.

Pros:

I like that I can really easily navigate between the projects because I am in multiple projects at once. I really like the possiblity to customize a lot of things, mostly the kanban board lanes and tickets details. I love linking feature, I find it really useful and I use it a lot. What is very important to me is also the Tempo application and I like how it's integrated in Jira, so I can really easily log my time into proper tickets. In our company we also use the Bitbucket and Confluence and I really enjoy that I can easily create feature branches, commits or pull requests from Jira itself. I also like the report tools to control my overall work.

Cons:

I have a lot of diffuculties with Tempo application search issues feature. Since I am participating in a lot of different projects it is really hard to search proper ticket, neither using ticket code nor ticket name is not functioning good enough. Sometimes I feel also overwhelmed with the amount of features which I don't use at all and I am getting lost in the user interface.

Advanced Project Management tool

Comments: As a software solutions company, we have numerous projects on the go and use Jira to track them. We use Scrum, and Jira matches up with the Scrum process well. We do weekly sprints where we review the backlog and add tasks to our sprint, and this process is easy with Jira and allows many options.

Pros:

Jira is a nice and powerful tool to track our projects. This includes all Epics, Stories, Tasks, Sub-tasks and bugs. It allows for many options as well, including labels, easy prioritization (drag and drop). Recently they have added features to help track milestones, so you don't need MS project anymore. There are a lot of different reports (good for clients) and numerous integrations available.

Cons:

After you get to so many users, the costs increase quite a bit. Confluence and some add-ons are also additional costs. We have also found the odd bug. For example, the wrong ticket is updated, or in the backlog view the mouse curser can no longer select rows (fixed by a refresh). Classic Projects vs. New Project is also a bit confusing. It's hard to get new features for some of our old projects, unless we recreate the Project from the start.

Alternatives Considered: Trello, Microsoft Project, Basecamp, Wrike and Asana

Reasons for Switching to Jira: We chose Jira as our team has experience using it already.

Business analyst - Awesome tool - Software administration

Comments: It's been a great experience using this tool for me

Pros:

As a business analyst, I have been using Jira for last 3 years and I think it's the best software management tool around. I have found it really helpful when it comes to providing upgrades to the projector to administer a project in development stages. It's all in one package. It has the board where you can re-protize your user stories in backlog by shuffling through pick and drop feature for the development team through tasks as well as can prioritize issues reported by the customer. You can write the user stories and just need to manage on the board. You just need to monitor the board to track the progress of the critical item and estimate overall progress. Workflow templates are available that can be selected to select the process a team wishes to follow or a path to take to address the release or apply patches on customer system. You can add the workflow by create one in the system and add the additional steps like unit testing, system testing etc as per the team. Another helpful feature that I love about this tool is that I allows integration with multiple other tools that makes it even better. Overall I think it's a remarkable tool that is making the software handling experience easy and simple.

Cons:

The only thing that I hate about this tool from atlastian is that it have a lot of the patches applied and part of constant changes. We need to scratch for sometime when configuration have to be modified or any existing thing changed. It takes for a while to get your hand adjusted on the system but when are down it's always good experience using it

Review on Atlassian JIRA

Comments: Overall, JIRA does the job for our team and even though I am on the Systems Team, we ourselves are mostly users as well. That keeps the headaches in check (as things could be very frustrating when trying to administer the applications. See above for the reasons).

Pros:

A team needs a ticket/issue tracking system and JIRA Atlassian seems to be used widely in the industry. As a user, it's easy to use for the most part. Besides having the option of hosting the application in-house, it also has the Cloud edition so from the Systems Team perspective, there's no need for servers, backups, security, keeping the service up (with fault tolerance), etc.

Cons:

From the administration aspect of the software, JIRA still has a long way to go: 1) As an administrator, as far as I can see, one can *not* even do such a simple thing as change the Display Name for a user (I suppose it's a "feature" but I can't see why that's a good feature). Instead, an invite is sent out to the user, who can then set the Display Name after signing up. 2) As an administrator, one can login as another user to test permissions. That's normally a nice functionality for administrators. However, for some functionalities, while you are still logged in as another user, you suddenly go back to your normal identity. That's very confusing and thwarts the purpose. One potential good use is being able to login as another user to set/update the Display Name (see #1). 3) Setting permissions is not that easy. I tried to set permissions for an account that's used for scripting (using the REST API) but it seems very difficult (really, it should be easy) to get the permissions done correctly -- sufficient but minimal privileges. 4) The REST API is not great. The online documentation is often outdated and sometimes things don't work (with errors). Even when things run without errors, it might not actually do the thing that it's supposed to do (so you write the code for nothing when you expect it to work).

A giant of software development

Comments: We've been using using Jira since the begining of the company about 5 years ago and we are happy with it. Their integrations with bitbucket and other atlassian software is also a plus for us. It delivers almost everything a software company needs to develop projects, and you can find almost everything else in their marketplace.
However we are likely going to change software soon due to their pricing jump after the "startup" tier.

Pros:

Jira is an incredibly large and flexible tool to the point that you can virtually have any kind of project - software or not - managed inside it. But though it is large, it is also relatively simple to being with and can accommodate simple workflows even for smaller teams, with some neat ready-to-go templates. But its abiity to grow into a platform that can support a large corporation is amazing. Scalability is definitely their main power. Jira also bennefits from a very large marketplace of plugins that can bring more functionality and fit the granular specificities of each company or project. It also has a very cheap pricing for smaller teams.

Cons:

Some basic functionality if just not there, which is rather unbelievable considering the size of this tool. For example easily planning a sprint, doing capacity tracking or even moving or changing issues can be very difficult and you may need to resort to plugins in their marketplace (with their own pricing). Some of the more advanced functionality (like workflows) is a bit complex and confusing and requires quite a bit of studying. Their pricing after the first tier (for startups) is just unbelievably expensive. It's a jump from $10 to $1000 when you add your 11th team member. Because of this we will sadly not keep using the software after that threshold.

Best Option for SaaS Development Management

Comments: After a number of years working with various tools, Jira is seemingly the best option for managing software development.

Pros:

I have used Jira at a number of SaaS companies over the past 6 years and have found it to be easy to use for the most part. It is highly customizable and easy to implement; we migrated our current process from Pivotal Tracker to Jira with relative ease. In comparison to other similar products I have used in the past, it exceeds the competition in flexibility, integration opportunities, ease of use and implementation, as well as configurability.

Cons:

I find myself running into minor bug-type issues somewhat regularly; like being unable to imbed an image in an item description at creation and only being able to do so in the edit view. Also have experienced issues with multiple users editing the same item and saving over one another's changes. Only issues have been minor that we've learned to work around.

Alternatives Considered: Redmine and Pivotal Tracker

Switched From: Redmine and Pivotal Tracker

The Go-to Agile Management Tool for the Enterprise

Comments: I manage a team of 11 people whose job it is to engineer and install a crucial piece of monitoring throughout the enterprise and use Jira to assign and regulate their workflow.

Pros:

We began our Jira journey years ago and have been using the tool successfully for just as long. As a team taking on Agile methodology in an enterprise where is was a very new concept, we needed a tool that was easy to learn, intuitive to manage and one that provided integration with extensions for our Agile ceremonies. Jira provided all of these things at an affordable price that has kept us working at a large scale enterprise level for many years. Navigation is simple, intuitive and while there is a small learning curve, most of our new team members have been able to pick up on things within the first few months. As our team's ScrumMaster and Product Owner, I enjoy using this tool to manage sprints and stories and generally never have to wrestle with the tool to make it do what I want it to do.

Cons:

The only drawback I have had with this tool is that sometime extension/plugin management can be a pain, wherein it is tough to locate what you have overall and how it is costing you. We've also had issues with duplicate versions of the same extension/plugin that led us to Jira support, which does leave a bit to be desired as it took a while to arrive at a resolution.

Alternatives Considered: Azure DevOps Server

Jira is an excellent tool for organizing tasks, tracking progress, and collaborating in a team

Comments: Overall, Jira is a powerful yet flexible project management software that has become a go-to tool for me. Its customizable features and ease of use make it a great choice for anyone looking to improve their project management capabilities.

Pros:

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.

Cons:

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!

Enhancing Productivity and Collaboration with Jira Software

Comments: It simplifies project management, issue tracking, and agile development, resulting in increased productivity, faster delivery, improved collaboration, and data driven decision making.

Pros:

It has some really useful features like customizing how you work, support for different ways of managing tasks, and keeping track of your work. It can also connect with other tools you use. While it's powerful, it might seem a bit tricky at first. Making it work smoothly with the tools you already use depends on how complex your setup is and how familiar you are with the software. But the good news is, Jira gives you lots of options to connect things together. You might need some help setting it up perfectly, but it can be a valuable tool for getting work done efficiently.

Cons:

Some people might find It a bit tricky when they first start using it, especially setting up projects and making custom workflows. It's become easier to use over time, but it can still be a bit challenging for newcomers or those who aren't tech-savvy. Making it work smoothly with the tools you already use depends on how complicated your setup is. Sometimes, you might need help from experts to make everything fit together perfectly.

A project manager’s dream

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

Pros:

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.

Cons:

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