Jira Reviews

Project Management for Everyone

Comments: I have used it from issue tracking , agile management and now with Jira work management you can do waterfall management also.

Pros:

With its simplicity JIRA can be used by all kind of users Engineers, IT, HR, Finance. I have seen its growth from bug traking to kanban to scrum and now business projects. No other tool has this simplicity and versatility.

Cons:

limitation of scheduling, roadmap and timesheet.

Alternatives Considered: Oracle Primavera Cloud

Reasons for Choosing Jira: Primavera is not user friendly with poor UI UX

Switched From: Primavera EXPRESS

Reasons for Switching to Jira: JIRA flexibility is good. UI UX is great. Scalability on cloud. Easy deployment

Quite expensive but Useful!

Comments: It was awesome and everyone of my team loved using it

Pros:

Jira is the ONE project management tool you'll ever need

Cons:

May get expensive when your team size is quite big

Alternatives Considered: Trello

Reasons for Choosing Jira: Nifty was missing a whole lot of modern features

Switched From: Nifty

Probably Best for Bigger Companies

Pros:

The software worked well for workflow. However, for a small organization like the one I was exploring this software for, it offers way more than we need...for better or worse.

Cons:

For software management, Jira seems to be the primary workflow and project management tool, so there's little incentive for them to improve their offerings because there is little competition.

There are many programs to manage projects and teams, but they are not Jira

Comments: As I already mentioned in the example of use in the Pros section, from the simplest project (a shopping list), to the most complex, the integration of several work teams from different areas and several very diverse projects, You need software that makes work, communication and organization easier.Jira offers us that, simplifying the management, planning and management of issues, without Jira, order becomes chaos.

Pros:

I will give an example of how I used it on one occasion and the advantages of having had this software.I was hired by a digital marketing company to improve proprietary applications, internal APIs, creation and migration of landing pages made in WP for our clients, migration of PHP applications to Python, server management, diversity of containers... The DevOps who was doing all that work left the company.An external audit was hired that provided workers spread all over the world, Spain, India, Latam...So we find ourselves with a lot of work, from very different areas, work environments and projects of all kinds and just one person to manage everything.With Jira we all worked under the same environment to organize tasks, but above all incidents and bugs, and with the need to manage the priorities of each new element that entered our work boards.At a glance, I could assign tasks, review code, refactor or modify it, and upload it to the test servers. Review the tickets, with screenshots of the errors or the new results that should be obtained. Keep in touch with everyone from one place and also receive all feedback in Jira.It was months of hard work, without Jira it would have been impossible to manage it.

Cons:

Despite having Jira with everything necessary for software development, sometimes it becomes more complex and less visual than if we accompany it with some extras, also from Atlassian. So it is easier for some boards or planning to use Trello, GitHub or Bitbucket for continuous integration, Sourcetree to make the different branches and versions more visual, Composer for team collaboration...

Alternatives Considered: Trello

Reasons for Choosing Jira: It is expensive to maintain and you never get the ease of use and tools of software of this quality.

Reasons for Switching to Jira: It is more complete for incident management, priorities integrates better with other solutions

Jira has been an essential tool in managing projects, client issues/bugs, and enhancement tasks

Comments: My main reason for choosing Jira was that I wanted a solution where I could grant my clients access to be able to add tasks or bugs and Jira has worked perfectly for that purpose. I have a few clients where I do a weekly status meeting and Jira is our main focus in the call. We review all issues with the 'In Review' status and if approved, we move them to the 'Done' status. We then look at outstanding items and adjust priorities as needed. My team then has their marching orders for the week.

Pros:

The ability to assign priority ratings and then assign a task to a resource is great. I can then run reports to see all open, in progress, and done tasks by project, priority, or resource.

Cons:

There is a bit of a learning curve. Jira is an extremely powerful tool and sometimes a bit overwhelming. In fact, I would guess that my team is only using a portion of the features available to us.

Jira is essential for any IT company

Comments: Jira helps in every team process. It makes things much easier to manage. I couldn't imagine project planning without Jira.

Pros:

Jira is wonderful in many aspects and it is designed to be user-friendly, with a simple and intuitive interface that makes it easy for users to get up and running quickly. It is a powerful and flexible tool that can be used to support a wide range of software development projects and processes.

Cons:

Jira tends to be a bit slow sometimes and I think it may not be suitable for very large organizations or projects with a large number of users. In these cases, it may require additional resources to manage and maintain and that means more costs.

Alternatives Considered: Trello

Reasons for Switching to Jira: Jira has many features that my company requires for daily use and Trello is more limited.

Jira - Ticket Management Review by a Game Release Support

Comments: All good, very user friendly

Pros:

Tracking of ticket, monitoring and seeing the progress is easy,it also has email notification for any change or progress of the ticket

Cons:

nothing much, its a perfect ticketing system for me, compared to other systems that I used before.

Jira Software Review

Comments: Overall I have had a good experience while using Jira. There are not much cons available and it is a well developed and maintained software Service.

Pros:

There are a lot of good features I have come across when using this software. Some of them being:1. Prioritization - Very Easy to classify certain types of Tickets raised through Jira if they are Critical, Medium or low priority. Definitely helps to Manage on what issues need to be looked at urgently and Manage the tickets so they get completed on time. 2. Editing/Updating Features - Very easy to update the fields in the Tickets if there is an error. A thoughtful feature. Even allows to update the people who log the tickets on the progress. 3. Easy to Use - Very user friendly. When I was first introduced to the software I was skeptical on how to use it but after 1 day it was very very easy. Did not face any issues and always kept whatever was assigned to me up to date and ensured they got completed on Time.4. Collaboration - Makes it very easy to Collab with colleagues if your working on something and need their views or expertise.

Cons:

I have not faced much challenges when using Jira, but some additional things that can be improved are: 1. Issue Type - There should be a better issue type system that could come in Place. There are some issues which come up but the issue types which are available make it confusing on which type of issue to assign it as.

A macho application in managing project workflows.

Comments: We can keep every detail of the project in one centralized location in realtime to allow free flow of up to date data across tools, teams and people.Jira assists teams to plan,track projects and generate reports intuitively.We can effectively manage work and time.A great tracker of productivity.

Pros:

You can easily manage hectic and big project workflows.You can stay on track even when the roadmap changes.Has effective roadmaps that help to put up the big picture ,communicate plans with team members and ensure that teams stay on the same page.

Cons:

No dislikes.You can easily automate processes on one single platform.It is highly customizable.A great tool in scrum and development cycles management.

JIRA for Agile project Management

Pros:

JIRA is very easy to integrate with open source and other tools like Github and Jenkins for CICD

Cons:

JIRA customizations are not easy to clean up if migrating from on prem to cloud

Jira is the Best Project Management Software

Comments: THe best software for project management ever.
It's paid, but even for our size of projects, we still love to spend some money on it and enjoy the good project management.

Pros:

Everything ! the software is very powerful, it has a lot of options and features: - Scrum, Agility and flexibility of changing flows. - Security setup for every type of users. - A lot of features ( no way to compare it with any other software i know ) - Very simple to use - Sprints support.. - High Availability. - Awesome Designs ( old and new ). And so many other things i love about JIRA

Cons:

I wish the cost was a little more less for small sized companies.

Alternatives Considered: Trello

Reasons for Choosing Jira: Trello is very limited comparing it to Jira.

Switched From: Trello

Reasons for Switching to Jira: The amount of features and the ease of use. Finally, everything is great about JIRA.

The software an engineering department can not live without

Comments: Jira cuppled with Agile processes have driven the velocity and overall engineering teams to new heights at the company. I don't see a world where once you are on it you are with it for better or worse.

Pros:

First of all I want to say Jira is DOMINATING the market. There is little that Jira cannot do which makes it a no brainer of everything most startups and companies will use. I love that Jira for the most part is a one-stop-shop for Engineering teams, IT teams, Knowledgebase, ticketing systems. You don't really see issues with using Jira until you get bigger. The fact that I can link Jira tickets to my Git commits and add confluence documents to my tickets and google drive files ALL IN ONE is ourtagious and its something my company loves inside and out.

Cons:

Just like every software out there you cannot be perfect in all ways. Because Jira is a one-stop-shop the biggest issues we have is customization of Jira. Not because Jira cant be customized, but only because it can be customized so much that we need set Jira admins whos sole job it is to manage Jira for the entire company because of the huge learning curve because it takes so much time how to figure out even the littest changes to make our lives easier. On top of that, a big issues I see if that as you grow in Jira it is a money pit at times to have it scale with the company. At this point, we are so vested in Jira we cannot get off of it. Adding SSO, and Confluence, and CI DI, and all the features that they promote arent dominating their fields, but its like "Well.... We are on Jira and they don't integrate well with other software so if we want the best features I guess we will have to use all their software"

Alternatives Considered: GitLab

Reasons for Switching to Jira: Like I said, Jira is leader in the market for Engineering teams, it makes the most sense. Jira is the best software for startup companies needing it.

Best and most true to tradition agile project/product management tool around

Comments: I have a (probably unhealthy) love for Jira and would need a lot of convincing to switch. It's interface is genuinely enjoyable to use and it aligns perfectly with agile product management methodologies, natively and in conjunction with its plethora of add-ons.

Pros:

Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.

Cons:

The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!

Alternatives Considered: Trello, monday.com and Asana

Reasons for Choosing Jira: Basecamp was rudimentary and unable to effectively visualise our cross-company/cross-team workload.

Switched From: Basecamp

Reasons for Switching to Jira: Jira was the most aligned with our internal development workflows and flexible enough to work for both technical and non-technical users.

Advanced Project & Task Management Features...But How It's Configured is Key to Success

Pros:

I've been using Atlassian products, JIRA in particular, for over 12 years. It's come a long ways in this span in terms of advanced functionality and additional configurable content, and it's consistently proven itself as a market leader in project and task management services. JIRA reporting, dashboard, task tracking, and project development activities are comprehensively impressively designed, easy to use, and highly collaborative for internal teams.

Cons:

The success an end user will yield from the software is highly dependent on it being configured in a manner that aligns with the business needs of the customer organization. For example, I've experienced instances where there are growing pains in how internal teams learn to standardize the way they tag tickets for project and task tracking and then use these identifiers to develop reports, create dashboards, and track schedules. If not setup properly by System Administrators then the ROI will be delayed, making it essential for teams to be properly educated and trained on the system. JIRA provides a wealth of content for training & education but worth noting the difficulty an organization can face if not approached strategically and with strong design plans during the discovery phase of implementation.

Highly flexible Agile project management tool but a little complicated to use.

Comments: I love using Jira as I can configure it as per my project's needs and I highly recommend this tool if your team is following 'Agile Development' process.

Pros:

I have been using Jira from last 5+ years now for Backlog management, Requirements management, Bug tracking and creating Dashboards for project review meetings with leadership. It's extremely flexible tool where you can configure your own workflows and customize it as per your project's needs. It's my go-to Agile project management tool (especially for Scrum). It's so easy to create and manage user stories, bugs, technical tasks etc. You can tag your user stories as per Epics and Features, you can also add labels to each ticket. You can track the status of any ticket and also see the bandwidth allocation of various teams. In JIRA, you can add advanced search filters to view only those user stories that has particular combination of fields (like specific assignee, status, epic name etc.). Moreover, JIRA Dashboard provides a bird's eye view of the overall project status which gives the real time visibility to you and the leadership team. The UI is very clean and simple and it makes Agile Development very productive, once you get the hang of it. Plus, it's very well integrated with many popular apps like Google workplace, workday, slack etc. But there is definitely a steep learning curve with Jira. The success of this product largely depends on how your management/leadership standardize various processes and workflows within Jira.

Cons:

Jira doesn't allow you to add multiple assignee on one user story, and this becomes a concern when multiple developers are working on one story. Also, it's hard to get support from Atlassian when you are facing some technical issues. Additionally, in my experience, I have found that as Jira provides great level of customization, it can become really messy, if multiple management styles are involved during project planning phase. The workflows can get overly complicated and as a Product Owner, you find yourself stuck in updating the ticket statuses all day long.

HelpDesk Dream System

Comments: Overall I really loved the platform and the easy of use and they offer a mobile solution which allows you to manange, support and assist using your mobile device which is important which you are on the go and have customers who diesire information or support.

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.

good tool for project management

Comments: Collaboration of our team has improved after we started using Jira, the tools helps in planning and identifying gaps while we develop features. The mobile application is really good and one can get work done from mobile app as well. Overall Jira suites our needs.

Pros:

Jira is very flexible and can be used for different use cases, eg: project management, issue tracker, road maps etc. It is quite easy to configure compared to other generic project management tools.

Cons:

The transition from old user interface to new one, it is very confusing, the UI is not consistent when we visit URLs from email notifications. Compared to other generic tools, Jira is quite easy but still it is not easy to setup, it takes quite a few days to configure the system as per needs. It would be great if there were boilerplate templates.

Alternatives Considered: YouTrack

Reasons for Choosing Jira: Pivotal tracker is very specific for project management, we needed a customisable product which we can use with our existing workflows.

Switched From: Pivotal Tracker

Reasons for Switching to Jira: JIRA was easy to configure and had all the plugins we needed, it was just plug and play.

Go Agile with JIRA!

Comments: Jira is very easy to use from the user perspective, as well as operating it from the Admin perspective. Overall I personally suggest this product, although its price not being very welcoming, it's definitely worth the money! If you're a very large organization you definitely will want to try Jira.

Pros:

Jira is a very good platform for organizing your team and projects using Agile/Scrum or Agile/Kanban. Whichever option you will choose you are covered! With its extensible platform through plugins you will never get tired of Jira. The installation is pretty much straightforward and with latest versions you can also make it HA, for instance on AWS, quite easily.

Cons:

Although the product is very mature, feels also like a big giant monolith although its plugin architecture. Also, plugins are too much expensive for just simple features. There should be much control from the Atlassian Marketplace, which should follow more an App Store logic like Apple's or Google's one.

Alternatives Considered: Blossom, Pivotal Tracker and Trello

Reasons for Switching to Jira: Jira is way more famous and most of the Agile coaches working in the field, are already aware on how to use and customize it, based to their needs.

Jira Cloud make tickets easy

Comments: Jira has been easy to learn and quick to expand. We started with a user base of around 10, this quickly became a 1000 in the space of three years. Every department uses Jira Cloud everyday for a whole range of different reasons.

Pros:

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.

Cons:

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.

Alternatives Considered: Freshdesk

Reasons for Choosing Jira: Excel was not great once a small business started to grow fast.

Switched From: Microsoft Excel

Reasons for Switching to Jira: Ease of use and it fit our model and gave use the options we needed to cut down on the time its was taking to track and monitor work flow.

Collaboration Platform

Comments: We are able to use JIRA to create, collaborate, test and deploy promos and emails for my company. I am able to see conversations and other notes from people I don't normally interact with, which can be really helpful in understanding issues that arise or other notes that may have been left out of conversation elsewhere. It's a great tool for us.

Pros:

I work for a large clothing retailer that often runs promotional coupons and sends out emails to customers. JIRA houses all of the collaboration for our company in creating and testing these promos and emails. What I like is that everyone, from the communications team to the Quality Assurance Team to the IT troubleshooting team can be in one place to resolve issues quickly. I love that there is the ability to tag other users and quickly get attention to issues that need a fast turnaround (emails and promos are often made within 48 hours from creation to launch). I also really like attaching 'sub-tasks' to a main project; This keeps organization a priority without having to search for every related task associated with a project. Related to this is the ability to attach documents right to any project/task for easy download. You can save searches and filters to your home page. For example, I have a filter for viewing only email projects, and another for promotional information. Once you get results, you can sort by title, date updated and a few other categories.

Cons:

At first glance, the layout is a bit overwhelming. You have a giant list of projects, and the search doesn't always bring up what you are looking for. It takes a bit of time to learn how to navigate. I would probably like to see 'tags,' or additional ways to categorize a project so that you can search for it through a few more parameters. For my needs, this isn't too important because of the short lifespan of emails and promos. But I could see other applications needing something like that.

Thoughts on JIRA from a non-programmer: Still easy to use

Comments: Tracking, organization

Pros:

I am a technical writer who used JIRA as my first introduction into working in a close-knit, agile programming environment. I really appreciated the clean design, multiple ways to accomplish tasks, and logical visual representations of concepts. Is something assigned to you? It has your face on it. We had several development teams working in tandem and JIRA allowed for each team to structure their sprints according to their own preferences (some had more traditional set up and others used kanban). As time went on we were able to add more projects to JIRA, after transitioning off of ClearQuest for our baseline fixes, and while there is certainly a learning curve getting established programmers who have used one system of tracking for 10+ years converted to using JIRA, most everyone was able to transition and feel comfortable within a few weeks. Speaking as a non-programmer, I found JIRA to be incredibly useful and easy. Tracking writing and editing projects through development didn't require any specific setup or features and it was all around a great tool.

Cons:

While it was great that every project could be tracked from our one JIRA site for my relatively small (30ish people) development team, any time fields needed to be added for one specific team to track something for stories or bugs, it was there for everyone. This led to having rather cluttered add screens that meant for a good deal of scrolling. I know some of this was surely user error, but having a bit more control would be nice. Also, the search function occasionally would just... not work. At all. As adorable as the sad faced little magnifying glass was when this happened, it would be very frustrating to lose functionality without warning. Being browser-based always makes for risk and some days would just be constant checking of if JIRA was up again so untracked progress didn't fall through the cracks.

Flexible, powerful, simple to use and grows as you go

Comments: Jira surprised me as coming across simple yet being incredibly powerful and versatile. It is a full blown Ticket and workflow management tool and it might be too much for small or personal projects. However, not being required to change the ticket system when the company or the team scales or are faced with types of tasks you did not expect is simply fantastic. Keeping software simple, easy to use yet increase its versatility and power is a virtue and Jira is build upon this virtue with care and vision

Pros:

Jira is clean and it is simple yet powerful. You can use it for your basic ticket workflows from the get go and expand as you grow or the tasks you wisch to cover branch out. It is easy to customize the ticket views to contain the information you want to use and avoid cluttering. The Workflow editor is one of the most powerful I came across in all my professional career. It might not seem so much of an importance but believe me, when your business grows unexpected necessities will arise and you will suddenly be required to track tasks you never though about. Jira will have you covered and allow you to add different task types which traverse task-type specific phases and have corresponding stati. Also you have all the world of notification and responsibility tracking ping-pong covered as you go. Two further things are woth mentioning: First the Atlassian World (the Wiki Confluence and build system Bamboo and many other products) integrate flawlessly and it actually really makes using them fun. Jira is one of the tools, that make you smile when you are required to use it no matter the task to track, its jus smooth, convenient and above and beyond provides a rich ecosystem for free and commercial plugins even for rather exotic use cases. Also, the license Model behind it scales fantastically. When we introduced it we were a small company with 8 people (we are now going strong towards the 200) and it was critical to keep cost for our tools reasonable. Jira got us covered.

Cons:

When we scaled, the License was not as flexible in higher user tiers as it was in the lower ones. Also once upon a time an update went wrong and we had to invest a bucketload of time and brain power to get everything back up to speed. We did run jira on premise and hat some custom plugins so there might be some of the tripwires: In case you use plugins they must be available in the version you wish to upgrade to and this might require some research prior to updates. Also, you can make a science out of the workflow and notification configuration. In case it is not documented well when you do it it might get you into trouble.

The best tool for a product manager

Comments: My experience has been great with JIRA and I have setup the product in my last two organizations. In my current role, the entire company has moved all their projects to JIRA. Despite some pesky UI bugs here and there, JIRA does everything that I need and has become a critical piece of my day-to-day work. It's never easy to build a product for product people, but JIRA has found a way to do most of what I need. I only wish the business would invest a bit more effort into their support team, but since many companies are already using JIRA, the internet has become a great substitute.

Pros:

JIRA gives me so much functionality out of the box. Within five minutes, I can create a board and invite my whole team to start working with me. It doesn't take long to customize your presentation of work to make it specific to your business. It has become the standard for the industry and with good reason; JIRA gives me everything that I need to track performance and ensure a timely release.

Cons:

There are occasionally some annoying bugs that will present themselves, but it's never something that really prevents me from using the product effectively; usually it's an annoying UI bug that looks messy or ugly. For the most part, many of the people that complain about the product just don't know how to use it 'as is out of the box'. The more configurations you try to make, the more problems you can create for yourself. Aside from this, their customer service is quite lackluster and it often takes days if not weeks to hear back from support - usually the bugs are fixed before you even get a response.

The "Ticket or No Ticket" Debate

Comments: It took time to get buy-in from the entire IT department to fully utilize JIRA. However, now that the whole department is all-in, JIRA has truly made our work effort much easier. We now have internal business partners who utilize JIRA to review work status, set priorities, and create new tickets when issues/upgrades present themselves. With an organization our size, I can't imagine not utilizing something like JIRA...not sure how we did it all in the past.

Pros:

The best part about JIRA is the ability to keep track of all work being done via tickets. I love that JIRA works for all kinds of styles of work. We work within an Agile environment, with some teams using Scrum and other teams using Kanban. No matter how the team is structured, they utilize JIRA tickets. This is great because there is a single repository for all work being done and we can easily search for tickets across all the different teams. The use of Epics vs. Stories is very easy too. We can keep track of what tickets belong to which effort with ease and show the progress of work through the tickets. We can also easily maintain a backlog of tickets. If two separate people submit a similar ticket (or at least two tickets that reference the same work effort), we can combine those tickets easily so that we aren't feeling overwhelmed with more tickets than actual work.

Cons:

The biggest debate among our team members is when it is necessary to create a ticket. JIRA has created a culture of needing to log every little thing, even if it takes just a moment to complete the work. Sometimes, it takes longer to create the ticket than to complete the task at hand. That tells me there is too much reliance on JIRA to report work completed. It causes some in management to show that their department is succeeding simply by the number of tickets completed. But the tickets don't tell the whole story, especially because there isn't a time component to those tickets being completed.

A very powerful task tracking system

Comments: JIRA is easy to use and great for managing work tasks on a project, however customization options are often only available to admins.

Pros:

Our company uses JIRA to manage work tasks. It has all the important features for assigning work to team members, tracking how long each task takes, notifications, capturing comments and hours worked. The tools allows for the flexibility to create your own JIRA ticket types or categories, with any kind of number of input fields. Data fields may be dropdown boxes, tags, values, or free text. Fields inherently have the ability to recognize hyperlinks and add those in once you type out a link, and it also recognizes JIRA links, such that if you enter a JIRA ID tag, it automatically creates a hyperlink to that JIRA entry. JIRA supports Agile development schemes and tickets could be easily tracked through a JIRA Dashboard. JIRA filters are also easy to use. You may use the basic query that provides you with simple dropdown fields for common elements, or you can create more advanced queries using JQL.

Cons:

Being a JIRA user can be limiting as you only have the ability to enter data for the fields that are currently configured. You have to go through IT or the admins for any form of customization such as adding/removing/hiding fields, setting what kind of text format is in each field (e.g. plain text vs rich text) and modifying which fields are required vs optional. When you have rich text formatting, sometimes it can be frustrating getting the text to show up the way you want. The workaround for this would be to use the Text tab instead of the Visual tab so that you can modify the formatting tags.