My Overall experience in JIRA is 3 years at this point and we started using it from the Year 2016. This is used in an project called recovery with the count of 25 developers from India/USA/Canada and several business end users on the same. The stiry was easily created and went thruough several phases till deployment. I would say JIRA ease my works in managing the stories since I am the PO for whole board and connecting developers/business end users for moving the stories and completing the same.

Basically there are lot of likes about this software: 1. Clear Tracking of what is going on in the project along with version needs to be deployed. 2. Ability to Use Kanban, Scrum and other Agile methodologies in JIRA Software. 3. Ability to flag the stories which is in impediment which will show to everyone on when it was started and when it was impended. 4. Easily keep tracking of Backlog for future works and deployments that needs to be made. 5. Ability to bulk update the stories for certain categories like version, points or any others. 6. Easy in terms of reporting to generate using JQL (JIRA query language).

Some of the cons in JIRA are: 1. Some times it was ended with deadlock leads to slowness. This happens when certain users running the report across the JIRA. 2. Security is less since we can see any ones board and get to know the statuses across the enterprise. 3. JIRA is costly since it per user licenses and whole organisation have to pay according to the usages.

As a tester, I am using Jira daily. My main activities are creating/updating bug tickets, updating task statuses, arrange and planning my future work. Jira is a great tool, on a basic level, it is intuitive to use. A huge amount of functionalities that are built in and integrated make work much more efficient. Bug and task tracking are easy and quick. Everyone with access can check what is the progress or the latest updates on a selected topic. Customization of features is amazing, Jira admin can adapt almost everything to the company's needs. If anything is not clear, customer service is happy to help and assist with all queries. In case the existing functionalities are not enough, it is a possibility to install external plugins from the shop that can extend capabilities. On the other hand, Jira can be problematic. It is a huge software with a large number of modules that can interfere with each other. Especially if modified by an inexperienced admin, e.g. a small change in a workflow can affect all projects that are in the company. It is vital to know what are you doing as an admin. Also, if users need new functionality, it can be reported in the Jira forum, which is tracking similar requests - unfortunately, a lot of them are there for years without updates, despite users constantly asking about that. I assume this may be because of the software itself, but explanations would be nice. All in all, it is an amazing piece of code despite the high price and minor problems!

A great number of functionalities. On the basic level is intuitive. Vast possibilities for adaptation and customization. Rather easy to integrate with other apps. A huge number of plugins. Customer service - in terms of personal help to do something

Some features are limited (e.g. filtering) Customer service - in terms of requests to add new/change existing functionalities. Rather high price

My use in Jira as a quality assurance officer is to manage, create, and follow up on Jiras to help developers with their work, the basic requirements for a good project management software are there however actual usability functions that allow you to make your work easier are not found. Everything feels slow and laggy and the search just breaks your heart since you can never find what you are looking for unless you know the Exact keyword or Jira number.

Jira helps you gather all the information about your development progress in one place. You can create different types of issues like To-DO, bugs ,tasks and epics. You are able to circle through different boards depending on your project which opens up the door for supporting a good number of projects while on the same web app. There are many helpful features to each "Jira" you open in order to identify its importance, priority and who is responsible for tracking and solving that "Jira".

The cons are down to accessibility, ease of use, and readability. Many features that should be automatically found such as easier Advanced filter access when searching, or viewing boards more easier, ability to click save instead of saving automatically which send unnecessary notifications to users. Cannot place notifications on specific projects when new jiras are created.

A great way to track deadlines between silos and especially developers.

Jira is out of the box free, and it's amazing because it works with everything by the same company. It also allows for easy organization of projects and silos, which intersect with each other. You can easily hand off tasks and allow people to collaborate.

Jira has a very development based angle, so if you're trying to manage a hybrid team, it works well. But if your team is marketing heavy, it's very anti-user friendly unless a person has familiarity with code or databases. It's just sparse and less user friendly.

I have used Jira in a few projects and every time it proved to be a reliable and productive solution. Mostly we use Jira to keep track of our developer's time in the Kanban board. It is a great tool that allows the developers to actually show us how hard they work and what tasks they tackled. Jira has increased productivity in all projects I used it in.

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

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

All our users/developers having no bad experience provide us and quickly access of what we need to do.

This jira web application has a lot of features to manage or agile projects from small teams to big teams from more than 20 people. Great connection with other applications like confluence.

Sometime it can be very slow when a lot of users using this portal. Or when there is a bug in a new version of jira when we cannot save or update tickets can be very annoying in a production project. Make sure that the update doesn’t brake anything.

The scrums boards are a delight to the heart while beginning each day of work. Work of software developers has become easy. Workloads can be fitted in a scrum board to manage the tasks effectively. It gives a view to keep a check on the completeness of individual work.

Sprint planning is easy and very helpful. Productivity is enhanced many folds after using this. Team work becomes stronger Easy to convey things between a team Easy to track team member's work Team performance becomes efficient Integration with tools makes the tasks efficient to process Product road map made easier than ever Used by software developers of Expedia

Certain limitations are:- In the beginning it is difficult to get used to it. Collaboration feature is missing It is basically made for software developers. A little expensive In the beginning managing tasks can be a challenge

Good tool for project managers and developers/analysts. Meets all modern requirements of a project management tool.

self explaining, a lot of ways to customize to meet your requirements in the project. Not only useful for project managers, but also for developers/analysts.

I have seen several instances and the tool seems to work a bit slow overall. Also when multiple users work on the same item simultaniously there are issues sometimes. Dark theme is totally missing.

Very useful , easy to use and track and monitor project management activities

We used Jira every day for development and Product management for creating, assigning and updating tickets ,user stories and tasks.

Though it's A very useful and easy to use and riched with features but scrum methodology I think Azure devops board is far better in sprint management

In a few words JIRA is a task tracking software that makes life easier when working on a project. Once the initial setup is in place (easy to do for common scenarios ) all is left for an administrator is to manage the list of projects and user accounts. Note that parts of the process (e.g.: customizing workflows) need to be done up-front, since this will become more complex once one or more projects are configured and in-use As for usability, it is one of the best tracking systems I've ever used: as a developer/QA you can easily update the status of your work in a user-friendly way. As a manager, you can always get the overview you need by just opening a screen or a report (most of what you need is in place by default) What's best about it is that as long as it is installed on-premises, it can be used as a central point of information for everyone involved with a project. The fact that it can be integrated with other common software industry tools adds further benefit from this. In the end, I should probably add that I've been using all kinds of bug tracking systems for about 15 years (starting with ancient tools like redmine going through PivotalTracker or VersionOne or JIRA) and almost all of them were either missing features that I deemed important or "spartan" usage/layouts that constraint the usage. JIRA just provides everything that's needed in completing a project out-of-the-box (whether it's Agile, Waterfall or Kanban or whatnot)

- Overviews & quick access to information - Possibility to integrate with most commonly used systems (it integrates with pretty much all mainstream tools, nut just the ones from Atlassian) - you can integrate it even with continuous integration tools or test management tools (e.g. TestRails) - Security control (everything is fine grained, tools to configure fine-grain access are already integrated - Comes out of the box with the most common work scenarios (client onside/offsite, development only/development + product management, etc) - Reporting (easy to extract the things that matter (whether this is worked hours or development velocity) - Version management (easy to manage what features are grouped in a release, or what fixtures were done for which version) - Workflows can be customized to match just about any real-life usage scenario - Allows for both on-premises (self-hosted) installation and cloud usage. - Configurable dashboards

- Pricing - it is prohibitively expensive for small companies, although they are making steps to minimize this with the new pricing models (e.g.: a few years ago they started allowing up to 5 accounts per project and unlimited projects, for a fixed yearly fee).

Working on jira is very easy, and makes all the work organized, I like to use it because it keeps track for everything, every ticket and comment and changes.

When I started using Jira, it was the first time I was in an Agile environment, it was perfect, the best features are the backlog, how to track tickets, and how to manage sprints, also the relations tickets is also important because sometimes tickets are dependent from other tickets which Jira makes it clear and visible.

Free tier lacks a lot of featuers, and some small teams don't need a big plan

Jira helped us to more easily manage multiple teams of software developers and gather feedback from end users for several large applications that we were developing which were at various stages of completion and usability. We were able to use our available resources in a much more optimal and seamless manner, which helped us to complete projects and resolve issues more quickly, easily track the status of specific tasks across multiple projects/teams and monitor productivity at various levels. Ultimately, this allowed us to both reduce development costs and complete our projects more quickly which in-turn increased our business revenue.

Jira is a very powerful tool for managing teams of software developers working on one, or even multiple projects simultaneously. It is very robust and feature-rich, with features such as setting up/managing individual tasks, coordinating development efforts across tasks/developers to maximize team productivity, managing/tracking issues & bugs, gathering feedback from non-technical users via Jira user stories and managing project backlogs. There in also embedded support for Scrum & Kanban boards, although I haven't personally worked with those features. The custom workflows allow users to setup and manage their projects & teams according to the needs of their business and their preferred software development framework and management style. Jira is a very comprehensive, all-in-one tool for managing smaller teams of only a few people, all the way up to very large teams of 100+ stakeholders.

Given the robust features and functions that Jira supports, there's a lot of depth and breadth to the software, so it can be somewhat complex and confusing to newer users, especially those who haven't worked much with project management tools previously. For project managers who are leading multiple teams simultaneously, things can get a bit overwhelming because the email notifications and project alerts can quickly start to become excessive, and there's no way to consolidate notifications across projects/teams.

I have used other project management software before and Jira is very simple and clean. It looks modern which is a big benefit that it has going for it.

I like that Jira is very easy to use and intuitive for the most part. It is easy to set up and explain the features and functions on a basic level. Within the week, even tech illiterate people could use it well.

Some of the terms (“story points”) etc seem superfluous. There are a lot of functions in Jira that are nice but aren’t necessary.

We have been using Atlassian Jira and other Atlassian products in our project for more than 3 years now. Its been a pillar for us to track overall project journey, right from tracking small subtasks to huge milestones. This tool is best for scrum master to have a single screen shared during scrum calls and thats enough. This tool is been used here as a multi-purpose tool for agile development, project management, collaboration, issue/bug tracking, backlogs and development tracking. So I would say this is one of my favourite tool while working in this DevOps culture and I would definitely recommend to have this tool in each project lifecycle.

1. Supports Issue tracking, task management, project management and collaboration. 2. Easy to create user stories, divide into sub tasks, track the progress of the tasks, label, categorize and prioritise tasks and we can get a complete picture of project goals. 3. Supports different reporting such as burn down/up charts, velocity charts, estimation, etc. 4. Out of the box many integrations, including atlassian confluence and bitbucket integration. 5. Highly customisable dashboards and supports sprints and kanban boards. 6. Task notifications and linking of tasks to other dependent tasks.

1. Sometimes it takes very long time to refresh/load the board. 2. Quite a learning curve since lot of features and sometimes becomes complex for new users. So initially its kind of time consuming to put efforts in learning the tool. 3. Sometimes get unknown token error and then we have to reload a page.

It is been amazing and it helped us to get more organized during the development lifecycle of our products. Also, it could be very powerful on the automation side by adding a few add-one from the market place.

It is very flexible and customizable which makes it easy to manage every different kind of software projects whatever the size of the product is.

The flexibility of the system comes at the cost of usability, so it is a little more complex to use the advanced feature of the system like their query language

I like JIRA a lot more than our old issue tracker, Trac. It's faster, and has a much cleaner, up-to-date UI. With the way our team leads and administrators created issue workflows, there's a lot of steps for the developer to do before a task is completed, which can be annoying, but keeps the devs honest and forces us to write down all the necessary info.

Jira has a clean, updated interface with powerful issue tracking features for managers, team leads, and developers. Features I like the most are the advanced issue search, integration with Confluence, easy navigation, quickly create new tickets and build sub-tasks, epics, etc. out of them. Our management and team leads like all the labels, components, and other content management features of the tools. If used correctly by developers, JIRA makes it easy to trace-down issues, and understand decisions made in the code. You can notify other users of issues with easy "@username" in the comments.

Formatting text can be a little tricky. Kanban boards don't come for free for all users. Sometimes it's slow in updating tickets (granted that could be our server it's hosted on...).

We have used Jira as CICD tool. It's easy to integrate. Easy to track project goals.

Jira is a great product for not only CICD but also tracking of project

Looks complex to use sometimes. Menus are not always user friendly

The complete development process can be managed with a variety of features and tools, from source code management to deployment and monitoring. Interaction with a variety of external tools and services to increase its flexibility and capabilities. It is a strong and customizable platform that provides a number of tools and services to support DevOps procedures.

It has a customizable architecture that supports a variety of procedures for development and deployment. The software development lifecycle is automated at various phases, enhancing teamwork between the development and operations teams. It provides a useful and effective technique for developing, delivering, and overseeing cloud-based applications.

When there are many users using this portal, it could be very slow. For some more complicated tasks, it can be challenging to use. It can be necessary for team members to take pricey training courses and learn new abilities.

It is purpose built for managing software development. For that it it very well suited from stories to bug fixes in the life cycle. In devops, there are great integrations and strong capabilities for stand-up, deployment, upgrades, and changes in operations tied to triggerable events from JIRA. In an ops environment JIRA is a workable tool, but is not ideal. That said it may be worth compromising to have a single tool across the entire organization.

While JIRA is the go to tool for dev and devops, it is weak in an operations environment. Time tracking and assignment of tasks are highly manual. Queue view are customizeable, but difficult to manage at scale. Analytics are very very poor. I tried exporting data for analytics on DOMO. While I could get that to work, the process remained highly manual and therefore not a workable dashboard environment. JIRA tools, widgets, and dashboards are reasonably customizable, but again not purpose built for ops. For example, time tracking is not start/stop/context driven.

We used JIRA in our recent projects to manage the development in the Agile way. The support of JIRA made the coordination and releases more and more manageable. As long as we followed the Agile best practice, we gained the tracability, ownership and project status in a straightforward and intuitive way. So the developers can focus on what they need to develop, managers know the status top down.

Jira is becomming more and more popular. Together with Confluence, Github, Jenkins. it offer platform to manage the projects into a well-designed hierarchy. Keep tracks of the relationship between requirement, task, development , deployment and release. It integrated with Confluence for the knowledgebase. Github to the soucecontrol and defect tracking. Jenkins for the deployment. Big community are making it better and better.

I didn't like Jira at the beginning. While that was about 12 years ago. The recent releases are much more mature. Not too much to complain.

A small business team of 5 development staff used JIRA for a number of years very successfully. We relied on it daily to plan and manage our software development tasks. For medium to large teams of software developers, I would highly recommend it. But for a small team like ours the admin overhead to keep it up-to-date with plugins and complex update release processes which usually meant some downtime, was too much.

Very customisable, server version great for installing in house, integrates well with other software such as Confluence. Fast and effective project and development management software. Excellent support.

Steep learning curve. Admin overhead too big in the end for a small team to keep core product and plugins up-to-date.

Once I started using JIRA, my productively gains were so noticeable that whenever I'd start a new freelance project I'd set it up for myself even if I was the only developer. It helps me easily scope out a project, line up a todo list and start knocking out items without trying to remember what next. Also greatly increases visibility for non-coding management/stakeholders into progress being made.

Excellent feature set and extremely affordable for small development teams. Easily setup Kanban or SCRUM boards, sprints and tickets for task tracking. For power users, offers a custom query language and tons of customization options to build a workflow that matches what works best for your team.

The only thing I disliked, was the inflexibility when it comes to attaching sub-tasks and bugs to existing tasks. AzureDev Ops supports an Epic->User Story->Task->Sub Task->Bug->Test Case. JIRA only supports 3 levels (Epic->User Story or Task or Bug->Sub Task).

JIRA allowed comprehensive communications between various departments (i.e. designers, developers, graphics, testing, QA) so that everyone knew the status of "events" real-time.

In my role as a Project Manager for software development, the developers used JIRA to manage the development cycle and we jointly use JIRA for problem reporting, testing, quality control and resolution. JIRA provided and tracked the information between groups so there was no confusion as to the status of a particular issue or trouble ticket. The ability to review "tickets" and see the status was very beneficial from a management perspective.

There was somewhat of a learning curve just to get started but that improved with repetition. Although I was not directly involved with setup and configuration, that seems to be a little more complex than originally though.

If i have commented anything on any issue where i am not assignee or reporter then i didn't get any report. Like wise if i got an assignment to complete testing of 100 jIRA Items which was logged by Manager & assigned to developer , then we need to add comment while testing . We can not assigned it to ourself then how does user should get a report of that.

Anyone can generate report report , track issue , awesome application .I found a bug please go through whole fedeback.

Bug Found on JIRA :- When issue list/keys goes to beyond 2 thousand numbers (For eg:- Project Name issue Key :- SAG-2001) then on Extracted/Downloaded CSV Report on windows OS , that extracted report is missing with First 2 digits of Issue Key From SAG-2001 , it is displaying as SAG-01 ) For more details contact anuradhagawande862@gmail.com. or +917972699213. Let me know how much bucks i should get for this bug?

I used Jira when assigning jobs. I like the fact that i could add a person to a job and they would receive the notification along with myself. So if i were away i knew i had a backup person who got the job requests. Maybe this has changed but I liked how all versions were kept together and you didn't have to scroll thru page after page to find a an older upload. I finally I liked how a creative project would then go on to the dev team to be coded and released.

Its been a few years since i've used Jira but after using other programs this one still stands out as the best. Easy to use, easy to track jobs and upload and great notification qualities. Can be used across the company from Creative teams to Development

I resisted using it for my team due to the fact that it looked too complicated but once our Dev manager ran thru it with me i saw just how easy it was to use.