Jira Reviews & Product Details

I really like how you can make Jira simple or as complex as you need. It is very configurable and flexible for our needs.

No dislikes - more like tweak requests - add a little bit more permission schemes around workflows.

Defect tracking, Feature / Task tracking, Overall project testing reporting and tracking.

Agile, Scrum, Kanban, Project Documentation & Requirements, Meeting Notes, Issue Tracking, Progress Reporting, Workflows, User based permissions I am a Manager of Project Manager and I run a massive program with several scrum teams, including vendor and partner relationships, spanning 10 different companies, in 15 locations around the globe. We share a single JIRA platform, with multiple projects and scrum boards, in order to keep all organizations, team members, and parallel workflows coordinated across the program. JIRA is by far the best scrum tool, and the best project management tool I have ever used, and I could not (and would not want to) do my job without it. Now that I have used it for nearly 2 years, I could not imagine ever going back to the way we used to manage projects. My and my team's productivity has increased by at least 5 times what we would have been able to manage without this tool.

There are a couple places administrative features could be improved to be more intuitive to use, but on the whole it is the most user friendly tool I've worked with!

We use JIRA and Confluence for software development projects. Specifically, I have been using this produce for nearly 2 years for mobile project development. We use Confluence for capturing all of our processes, requirements documentation, status reports, and meeting notes. On-boarding new team members is a breeze with our processes all documented and kept up to date in Confluence -- project plan, build / release schedule, defect logging instructions, UAT procedures, etc. The Confluence wiki pages are also a great way to keep a living, always accurate, version-controlled document your product requirements. The comments feature is great for capturing time-stamped product owner (or client) approval of requirements, and for the developers and QA to carry on a Q&A dialog with the BA, refining requirements. Never again will the QA, iOS, and Android devs have different interpretations of a requirement because someone wasn't included in an email chain refining a requirement, or an email got lost in someone's inbox. Plus, the Confluence pages link seamlessly with JIRA, allowing easy reference between development tickets and requirements. The Confluence pages also have powerful reporting macros for creating fantastic status reports that pull real-time data from JIRA. I also highly recommend the Team Calendar feature, where our team tracks all our vacation, OoO, sprint cycles, and major deadlines. I use JIRA to manage 5 parallel projects for my teams and our vendor teams. JIRA allows linking (and movement) of tickets and dependencies across projects. We have also used customized workflows so that JIRA accommodates our development and test flow. We even created a new issue type for Change Requests, with a specialized workflow, to manage scope creep and document client review and approval/decline of effort and cost estimates for incremental requested work. With JIRA, everything is documented and only a query or dashboard away from your fingertips! The comments feature (same as with Confluence) keeps everything related to a specific feature, story, or defect, all in the right place, and OUT OF EMAIL! The component feature allows you to configure default track owners for issues assigned to particular sub-teams. And I could go on about all the great features. It's the ultimate CYA and never let something slip-through-the-cracks tool. I wouldn't want to do my job without it! As far as support - Atlassian does a fantastic job of keeping a Confluence library of "how to" guides that are FANTASTIC for teaching yourself new JIRA tips and tricks

This product is wonderful at organizing and tracking collaborative work. No need for endless emails and phone calls. It's always easy to find previous work later. JIRA works great for agile software development processes as well as organizing any other type of collaborative work. Our group has one project for the software development and a separate one for the web content development. It is so easy to assign work to coworkers and get feedback on important questions. The many features and tools in JIRA make it extremely versatile: such as labels, epics, subtasks, linked issues, attachments, and a whole lot more. Notifications and JIRA capture are also essential tools.

I would love to use JIRA more on my iPhone. It would also be nice to be able to capture screen video using JIRA Capture.

This software is a project management tool that we use to manage software development and other projects. It facilitates comunication, timely work, and tracking of work for audits of all kinds.

JIRA is super easy for the non-technical people on our team who need to report issues and check on the status. It is flexible enough so that anytime we say "I wish it did X", we can turn around and do that 9 times out of 10.

We really really really really need duplicate issue prevention. There are features requests for this as well as ad ons but we run on-demand so we're at the mercy of the feature request.

We are able to communicate much more effectively. Meetings are a lot less critical since all the information we need to know is available in JIRA.

JIRA has an excellent workflow engine that can be easily configured for any type of needs. Workflow editing tool gives you a possibility to create a complex workflow only with drag-and-drop. On the other side, the workflow can be configured with various complex rules to be applied on status changes or on the external information. As an Administrator you can create and manage different types of entities, like "bugs", "user stories", or if you need "customers" or "projects". Dynamic views can be modified for each entity type, so that you have the information that matters.

JIRA installation on-premise is quite complex and requires extensive experience for System Administrator. Moreover, JIRA requires good infrastructure behind, that increases costs of the complete on-premise solution.

JIRA helps us to track progress of development projects transparently, easily and quickly. Automation procedures that are applied to the workflow process decrease the amount of manual work and increase the quality of status tracking and synchronisation of tasks statuses across multiple systems.

Very easy an effective, minimize the time spent in collaterals and concentrate on the core work. From an IT admin perspective we especially like the ability to customize it with custom fields and workflows. The rich plugin ecosystem greatly simplifies the addition of non trivial features. As integrator and consultants the low baseline price tag allows to introduce it easily to customers and then allow them to test drive the real product.

The handling of tasks and sub-tasks is very poor. From such a product you'd expect at leas some sort of WBS support.

Our main purpose is SW-related ticketing and helpdesk for customers. We use it very well also for consultancy purposes.

simplicity and integration with other systems

A not very well thought out UX with seemingly odd decisions made to "improve" the system

Software development / issue tracking

JIRA is a very intuitive platform that allows my team to tailor it to our needs. You can use it for as simple of a project to as complex of a project and still get a lot of benefits either way. I particularly like the ability to view all tasks in a few different ways (monthly, by epic, etc.), as well as view your sprint health easily through the dashboard. The advanced search is also a great function -- JQL (JIRA Query Language) is easy to learn, easy to use, and allows you to produce the exact reports that you need.

Prioritizing tasks on the monthly view with the drag and drop is a pain.

I use JIRA to manage an IT project and although there was a minor learning curve for some team members, most of them saw the benefits of a customized team dashboard very quickly. Each user added their own views (using the search/reporting functions) and it allowed us to have more productive daily stand-ups since everyone had a sense of ownership and an eye on the active sprint and things to come.

JIRA is a well-thought out product, configurable and usable by both developers and business users. Plenty of features, and part of a set of collaboration tools including Confluence for documentation. Everything about JIRA is designed to support growth from small teams to larger teams and enterprises.

Because it is easy to configure, it is also easy to construct overly-complex workflows. One rule of thumb is to start with the default workflow and only add steps that are absolutely critical to your process.

Managing the backlog was the biggest challenge, but as the company grew we needed collaboration tools that would enable us to work with larger teams as well as to move into project management.

Jira is the excellent bug tracking tool in the market. It makes the life easier for tester and Developer to log a defect

I like everything about Jira. There is so much to fill but it makes life easier for developer

Jira is the excellent bug tracking tool in the market. It makes the life easier for tester and Developer to log a defect. I have used in all the companies i have worked with. Currently using Jira as well

I like the endless possibilities of how you can use the application. We use it for everything from our SDLC to IT Tickets to internal project management and even a fully customized Test Case Management system. With just a few plugins, or the ability to write your own plugins, the possibilities are endless and you can get great benefits from the application.

There are a few inconsistencies in the application and some large gaps in functionality. Examples include: Project Categories have no immediate purpose except to group the projects while viewing the All Projects view as a user only. Another example is the lack of certain functionalities such as linking events so that notifications or other actions can be tied to built in functionality such as linking to another issue.

Better time tracking incorporated with issue tracking. Users can be in a single system to both track time and work on issues. Test Case Management is more intuitive and reporting possibilities are endless with the ability to link a test case or a test run to any other issue. We are also improving our SDLC by using Agile methodologies included in the JIRA Agile application.

- You can have everything from Bugs to Story / Requirements, wiki, Test, Meeting Minutes, KPIs (and so on) centralized in one place. Allows you to interlink them seamlessly. - An extensive community. Anything you need to know has already been asked in stackoverflow or somewhere else. - Full customization for your needs. - Several community addons (you can even make your own) for that little extra.

A few more default options for customizable KPI / Dashboards would be nice, but that's easily addressed by addons.

When you have everyone from Program / Project Managers to Developers, Designers and Testers using the same platform, everything is traceable and everyone is aligned.

+JIRA allows users to highly customize their user stories. You have the ability to add multiple types, for each type his own labels and screens. You can also define a workflow for each user story type. What are the statuses ? What are the transitions that will move the user story from one status to another. +Dashboards are very easy to build and customize and very useful and user friendly when you look at. +Sprints are the best way to plan your work. You have an amazing agile board to track your issues, prevent delays, follow up with assigned users, +A large number of plugin can be easily installed and integrated with JIRA. +JIRA can notify you on any object that you are following as a watcher to also be aligned with other team members.

The agile boards are a bit slow. We are planning to install a newer version of JIRA to fix this issue.

We are using JIRA so that our clients report their issues, feedback, new features, bugs, regressions. JIRA will help us centralize our work, plan it and track its progress using sprints. Issues will be analyzed by functional, fixes are developed and reviewed by developers, fixes are tested and validated by testers to finally put the issue as "Done". This workflow is allowing us to transform the client feedback to a real product increment, increasing the value that we are offering to our clients and maximizing our customer satisfaction.

JIRA is the best bugs reporting and scrum planning tool you can have. It's fast, reliable, flexible and very user friendly. You can also install addons that add more usefull features to your project's database. The liscencing price varies depending of the size of your company bit I especially find it very affordable for small and independant companies. You can create detailled dashboards for your projects. JIRA is not only perfect to report and track bugs for your products, it's also powefull to plan features.

JIRA is not perfect. It is the missing feature to custom the email templates for notifications. It's also missing the feature to have a default description and steps to reproduce template.

I am a Software QA Analyst, I find defects within products and I report them. I make sure our products meet all the quality requirements.

Some of the best features: * extremely customizable out of box to suit your requirements * native integration with other Atlassian products out of box * extensibility with its robust add-on framework * big community for support, 3rd party add-ons * mature API, allows you to extends its features yourself

The only downside to JIRA that I can think of is scalability. With its standard offering, once you reach million of record, it will start to run slow. However, with the new Data Center offering, it may resolve this problem.

I use JIRA to solve a wide variety of problems, including: * software development * general project tracking management * portfolio management * all purpose task management The power of JIRA comes from its ability to adapt to your particular business needs and you can customize and morph it to suit your needs. As a consultant and user myself, I have yet to encounter a situation where I cannot use JIRA as the solution. It does have its limitations out of box, but with its add-on framework and API, it is very easy for you to solve the problem with a bit of programming.