Jira Service Management Reviews: 4.2/5 — Solid Choice

The best part of JIRA is estimation and logging of hours by users. This way at the end of project we can accurate track hours and can improve on it.

The UI can be improved a bit and can be migrated to latest standards

-Planning -Project Management -Project execution -Bug tracking -UAT issues -Closure

I like the detail and the way you can break each issue into smaller "sub-issues" . The granularity of JIRA was fantastic. Also how it tied into subversion and you could track time right from GIT

It can be a bit overwhelming at first. but the curve drops off pretty quickly

We use it for internal IT programming bug tracking. Our testers used this platform to track bugs and then assign them to developers.

after using bugzilla and some inhouse tools using Jira for bug tracking is a feature rich experience.

People will keep asking for more difficult schemas :)

No maintenance of in-house tools, good support from Atlassian, it can integrate easily with perforce, git etc

There would be nothing that any one will not like about this application.

There would be nothing that any one will not like about this application.

We use this to track our application status and also defects that are created by the business users and quality analysts.

It's very user friendly and I can connect test cases and user stories here

It should not be slowing deleting and if allowing internet should only based on permissions

Reports generation

The way one can track work and link it with code changes, I really love the automatic integration of jira and confluence and when clubbed with hipchat these platforms are no longer like different things. They are just the same thing. It is really helpful in tracking the progress of any things some one needs to work on. I am using Jira every day to log the work I am doing and the fox enhancement stories of anything I work on and Jira is a great tool and very easy to do such things and apart from that one can track the work logs even up to accuracy of one minute so my manager now knows what exactly I am doing and really reduce time wasted in daily sync calls meetings and stuff like this.

There is nothing much one can wish for in ticketing tool. How ever a better documentation and some better integration options would be great in case one need to sync jira with some other ticketing tool.

Jira is really helpful in tracking the code changes and the things where the team is putting efforts. Apart from the Jira have made the job of manager way too easier.

Very easy to customize to your needs. Works for large teams and small. Also appreciate the robust API and integration capabilities.

Setup can be clunky. First creating projects and custom workflows can take time. Could be easy ways to quickly view/reassign/and bulk update items.

Need way to respond to clients and quickly forward context to internal developers for work. Also solves needs of tracking SLAs

The ability to track open issues at resolution level, ability to view historical issues for future training.

Learning curve for people who don't receive an official training...

Jira helps the clients open issues or file complaints with the reporting solution and helps to allocate this issues to the corresponding department for faster resolution and efficiency

Jira has done a lot of work making project tracking transparent and easy to use. it has really cut down on our meeting time and confusion since everything is stored in one place.

still has some limitations, we have not been able to successfully link our test cases to each ticket. I think Atlassian is coming out with a test case repository that might be more successful than what we use.

When an issue is reported you can be sure it goes into the correct queue, you can track how long it has been in the queue before being worked on, you can easily see how much of your time is being tied up on the same issue.

Easy to manage and adjust for our needs and change workflows

Usage of Sprints and Iterations, a bit confusing

Development workflow, easy to see status of all work

can setup your workflow and move the ticket for a project in different stages

if you have a project with multiple assets you have to move each single one

daily production for marketing automation tools eg email marketing campaigns, landing pages creation, nurtures , lead generations programs we also use it for our internal IT management , we send tickets to IT if something isn't working

The kind of view it offers, which is easily understandable and therefore resulting in faster issue resolution. The ease with which daily work can be logged and monitored. It also provides an option to track the issue which is indeed helpful as it helps me know the progress of the issue raised and also the name of the assignee. Also, the JIRA service desk provides wonderful customer support. It also helps us meet SLA. I

The maintenance of Jira can be improved. The initial set up is quite complicated. Also, the automatic session timeout.

Jira service desk has been an effective solution for daily issue tracking. The features like the addition of tasks, effort logging, easy monitoring of who is the task worked upon by. The team was able to add epics, user stories, tasks and also assign it to them. The Kanban board is very helpful in the quick monitoring of the tasks and also helps us know the tasks in progress /that are completed. Also, as we are working in agile methodology, it's really important to complete the tasks in the assigned span. And JIRA service desk has been very helpful in addressing issues.

Jira has all the options builtin. we are using it for bug tracking tool as a main

mobile app is some what difficult to navigate .

NA

Very useful for fast changing environment. We can distribute the tasks within team and great way of tracking status for the tasks.

There is nothing I dislike about the tool

Easy for tracking issues and enhancements

JIRA is good for UAT purpose to log the incidents related to defects

UI can be improved a bit so that it's more friendly to use

We use JIRA for UAT defects log and Patching related issues log.

Its a wonderful tool which helps you manage the tasks among the team. You can distribute the work among team members and see how much task is completed or pending. Single interface for everyone in the team to be on same page.

There is nothing I dislike about this wonderful tool.

I have created JIRA tasks for my team members and assigned them. They can go and see whats the next issue or requirement they need to work on and mark the status as and when they finish the task.

Customer portal, powerful workflows, integration with other Atlassian tools

Cost is a bit of a concern, especially with the smaller organizations

Trying to connect customers with our internal service desk that solves customer related issues

The ease of use and flexibility to accommodate new changes

The UI is not very intuitive and doesn't appeal

We use it for both issue tracking as well as our SCRUM backlog

I really like the ability to send a quick message to those that are in need of fixing issues across multiple departments.

The complexity for being an engineers tool, if you're not an engineer it's tricky to navigate at first.

Cross department issue tracking and we've found that we can only increase the ability to improve through this tool.

The short time it took to actually learn it. I used it for a week and felt pretty confident handling the resource on my own.

Nothing much I could find wrong with it in a weeks use. I would say a little more modern tutorials on the subject would help.

Quick and detailed IT support desk resolutions. Much easier than others I've used.

Open source, intuitive, collaborative, user friendly

Not many things I dislike pertaining Jira, may be it can also Provide access to sprints closed and historical tickets associated with them

User stories, bugs

The service desk help a lot to track different IT support activities and provide a tool to monitor the SLA provided by compny that is working with us.

What I dislike is the same of all this kind of tool, the deploy to the user give us the chance to provide a best service to the final user, because we can provide a layer to share the support with also some external company to cover different time zone, but for the user that in the past was used to have a direct contact or a phone call sometimes this doesn't seem an improvement but the see this tool and also the other similar too cold and the perception is that this is impersonal and not help like the normal use to go directly to the tech people

We start to use this kind of tool during the migration of our ecommerce to aws, but now we are working to open this to all our users, expecilly for the sales people to provide the best help when thery are with the customer

Ability to add link, refer to attachment in comment

A bit complicated to get used to at the beginning

Customer's tickets

The tool gives me the hand of the blocks that I can build on my own. This gives you almost unlimited possibilities. The proposed approach does not limit me nor does it need to bend business processes to the system. It is JIRA that adapts to our business and grows and develops with it if necessary. This provides a sense of security and confidence that we will not come across some limitation that will stop us. There is no need to circumvent problems, but on the contrary, we can solve them here and now in the best possible way. Looking at other tools, I find it hard to get the impression that they are enclosed within certain frameworks. Knowing the JIRA is hard to deal with. I recommend to everyone who is interested in efficiency, flexibility and sense of security.

At this moment I can only say that when I can not do something I usually have to look for documentation or community answers. Usually such answers can be quickly searched.

Support service calls, project management, work time recording, and many more.

Ease of use, integration with JIRA Software, style, customization

Unable to integrate with JIRA Core, would like conditional logic in fields so they can hide/show depending on input

Service tickets, project management, issue prioritization

JIRA is great software that allows me to communicate with our IT Team, and let them know what changes and updates we need.

Nothing really! It's very intuitive, though I don't like how things are structured internally at our office. We don't always have a say in priority, but JIRA allows you to decide what tasks are most important!

Business problems like web development for UI and UX are solved by communicating them through JIRA. It alerts IT and keeps us in the loop for those that report.

SCRUM and JIRA are the best combo and having also support to kanban gives a full power on the way to handle a project and that's what I like the best

I would love to be available to assign a ticket to more than one person that would be handy, also the way to handle comments and tag people it's kinda difficult to understand how to get notifications about it

We use it for everything that we do on the company and with customers for use it has become the primary tool to track projects under scrum methodology.

The ability to look at what tasks are assigned to me and team member updates. JIRA helps in making the group work easier and to communicate with the team members.

The only thing that I dislike about it is maybe I don't know if the feature is there, but it does not send me desktop notification about my deadlines. I would love to have a reminder alerts feature.

We are using JIRA to streamline our projects and also to track our application development activities. It also helps in collaborating with the team and knowing who is up to what tasks. Some of the benefits that we have gained by starting to use JIRA is: 1. Ticketing system for problems. 2. Project management 3. Documentation 4. Activity tracking 5. Team collaboration.

I can update and easily aquire the project status and also easily assign the projects

Nothing really but how bout changing its theme a bit

We currently assign task to our team through it. And thus we come to know which task is performed by whom

I love how you can create a custom flow for testing Test Cases. I've been on several different styles of projects and each project was able to create a flow that worked for it and made it very user-friendly. For my current project at work, we are able to use the buttons to go from QA Ready > QA Passed / QA Failed > UAT Ready > UAT Passed / UAT Failed > Code Review > etc. Being able to just click the configured button makes it idiot-proof. I also like that there are a lot of ways to track progress on interconnected tickets - you can tag the ticket and have it turn into a link, you can link the ticket and select from multiple different (configured) reasons why they are connected, link two ways, etc.

The user interface seems a bit outdated. It could stand to be more sleek. The fact that this is all I could come up with for dislike should be a testament to how great the product is!

I have used JIRA on many projects, mainly for testing and QA purposes. We also use it to track development tasks.