Jira Reviews: 4.3/5 — Solid Choice

I enjoy that there are different views for the same information, active sprints vs. backlogs

My dislikes are what my company uses if for, not the program itsself

We are making the work our team does visible to one another

Moving items on talk board for Sprint and Backlog planning

Data entry could be streamlined for details

Agile

Overall, we now have a system where I feel that the requirements for documentation are communicated well.

It's only as good as people using it. We have somewhat recently changed to a "subtasks" system, which makes measuring metrics difficult.

We have a rapid delivery and release schedule, and using JIRA allows us to communicate with each other and with our customers.

We use JIRA to track and manage all of our marketing web requests. I like that it has drag and drop capabilities that make it easy to move tasks to different sprints. The ability to categorize tickets by epic and also create subtasks is nice.

The interface is a bit dated and could be more modern. Not easy to use on your phone which is limiting for me as I like to work via my mobile device often. wish there were more workflows and more integration with other tools.

We use JIRA to track and manage our tickets so that requesters get notifications and we can see workload, resources, etc. We use an agile methodology and have set our instance up to allow us to do sprint planning.

Massive capacity for complexity and technicality

Can be cumbersome and overly complex for your average project management functions

Implemented to handle BI functions but phased out in favor of a simpler tool

I like how configurable it is. Workflows, setup right, can be really powerful for keeping work on track and ensuring quality.

It's really hard for new users to get their head around it. The interface is a little cluttered and it's not clear what needs attention and when.

Tasks management and team collaboration.

Smoother to move projects along the Knaban than working a traditional whiteboard. Easier to see twhere my colleagues are in their work.

It is a bit clunky to set up/change the steps your group has for the project progression.

We track progress on some of our projects.

There is a LOT of functionality in JIRA. Let's get that out of the way - so if you can become an expert, you could customize a lot of things to align with your process.

I felt like we didn't get the hang of JIRA until we got a 'superuser' through the door. It is really not easy for a new user to set up so it could be hard for younger companies.

We use JIRA for product and engineering management purposes - sprint planning / tracking, bug tracking.

Quick, works well with Mac on Safari and Chrome

Poor format editing, global date settings annoying

Ticketing, workflow management, task routing

It's a way to keep track of project communications and progress in one place.

For non-technical teams, it seems like an additional step that slows down the process for purely documentation purposes

It solves the problem of keeping all integral parties looped in on project communications and progress

it's generally easy to get going and start using once it's set up. The user interface is mostly straightforward and it's good for getting a view of the status of different work items. Best is the integration with confluence so I can see status of issues in wiki pages.

the user interface is clunky and isn't great for managing large numbers of issues.

tracking of execution status of our projects

the way it displays the issues and one can create the dashboards. The business is able to create their own dashboards which is very useful for bug tracking and issue resolving. The managers and other users can personalize their screens which h is also very useful

it keeps hanging and logs out randomly. The single sign on is a a issue.

we were able to track all the issues at one place. we made modifications and enhancements to meet our business needs. It is highly customization which is a great benefit for any organization

JIRA is very, very powerful. The filters and advanced search options can be useful, and tracking issues based on release versions (and dates) is another great feature for us to quickly analyze what needs to be done ASAP.

The whole user interface is confusing. You can only include some types of filters using the advanced search, which uses a specific language called JQL. You just can't assume every developer in your team is gonna learn JQL simply to make queries in a issue tracker, so there is probably gonna be one person on your team who knows how to make queries and will help the others with it. This is even worse for some people on the QA team, who might not be developers at all. The rest of the user interface is not much better - it seems like there are many menu items which just go to the same screens, and you'll likely click around randomly, hoping to get to the right screen where you'll waste some more time setting up the right filters. Definitely takes some time to get used to.

We use JIRA mostly for bug tracking, although some of the product management features are also used. Both our development and QA teams have access to it and use it to collaborate on the whole process from discovering a bug to releasing a fix. Having a way to track each issue (knowing in what part of the process it is, etc) is fundamental as the product grows in scope, which is the main benefit of JIRA for us.

It is complete, a lot of tools and ways to organize the tasks.

It is crowded, there is so much ways do to the same thing. It is not very intuitive.

Organize and keep track of the tasks at work.

Really detailed reports for projects I can give to clients for review

I have not found dislikes as of yet with the system

tracking, project management

In my opinion, the best feature is the ability to create sub-tasks and linking projects that are related but separate.

For an occasional user, the interface is difficult to learn. The text formatting options can be frustrating at times.

I use JIRA most often to divide and conquer large projects with multiple tasks working simultaneously.

It's very straight forward and pretty intuitive to use

The user face is very old school and does not have a modern, easy look and feel

Launching products on our websites, special conversion and optimization projects for our websites

I like visually seeing the different process steps a task or project is in.

I dislike being unable to delete or cancel a created task.

Jira helps us track work

What work looks like in the backlog and on kanban boards

reporting is much more difficult than it should be.

managing work. visibility into developers progress

JIRA helps us organize and prioritize bug related issues that arise with our software application.

Site navigation isn't the greatest for getting around. Not ideal for seeing high-level existing reported bugs

JIRA is great for collaboration internally on outstanding issues, next steps, and priority for existing bug-related problems.

I like how you can open new issues to ensure that things are being done in the proper amount of time.

The interface is boring looking and looks outdated.

Solving project management with clients. I can talk to client internal teams while working g for an agency.

I really like the operation of the work boards. They are very useful when you work as a team and plan tasks.

It is an application that has many features and it is very complicated to know where things are.

I use Jira to generate tasks, do weekly planning and organize with my co-workers. It is also very useful to record work times in each of the projects.

Ability to do many things, assign tasks, monitor time, track bugs, see progression in project completion to better give idea of due date.

Too many areas to search through to find what you need, not user friendly, difficult to learn and teach, did not like the set up of projects, task building/set up and file sharing within JIRA. Also, you must have a good team that follows directions and checks off their tasks when complete and puts actual time in.

Project management, time tracking to better estimate our time to bill the clients, bug tracking. We realized we undercut ourselves and did not put enough time into the timeline/budget for all that needed completed/fixed.

Jira can seemingly handle an infinite number of projects, tasks, and subtasks.

Jira can seemingly handle an infinite number of projects, tasks, and subtasks.

We're using Jira to manage creative team projects. The benefit of this is that it is the "one source source of truth" and everyone is able has a record of their work.

Replaces the walls of sticky notes from the old days. JIRA’s built-in graphing makes it easy to generate and look at burn downs and track velocity. Its integration with email streamlines communications, both between the sprint team members and external parties and stakeholders.

The burn down charts and projections may not emphasize the call for action by a team leader. Team members viewing the projections may turn into a self-fulfilling prophecy.

Collaberation and corrdination for a major software development project.

It is simple and straight forward. No need to know how to use it.

You need to manage yourself, TFS does it better.

Tasks with other team within the organization

I like that you can tag people within the assignments to directly tell people who needs to be doing what. You can also add all documents within the tool so everyone can be working off the most up-to-date document. It is also great since timelines can easily be added in the tool

I dont like how easy it is to miss part of the chain. If you are not a "Watcher" on a project, you dont see what stage that project is in unless you're being tagged

We use it in our agency to manage content creation processes. It is really useful for the creative team to keep them on track

Team management, ability to have everything in one place to go back to and review. Team collaboration

user interface is very technical, can be simpler and easier to use. less clunky

project management

What's nice about JIRA is as part of the Atlassian suite, it seamlessly integrates with the other Atlassian products that we use like Hipchat, Stash/Bitbucket, and Confluence.

JIRA is not a particularly well-designed or engaging platform. There is much to be desired there, something more like Trello (which ironically was recenly acquired by Atlassian) would engage the user a lot more. Trello is more fun to use.

We use JIRA to assign track bugs, tasks, user stories, product development and more. We make use of the commenting ability and the fact that information from other Atlassian software is directly and automatically linked in a ticket.

I like the email notifications and collaboration

Just kind of ugly and clunky to use, I have trouble sorting through everything and visually it all looks the same, it's just a wall of content.

Ticketing system, coordinating projects.