Likelihood to Recommend
Great to manage your issues in a clear and centralised way. If your development teams work with
, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Read full review
Kanban is well suited for a fast-paced working environment for larger teams who want continuous communication with users. Kanban is good for rapid development and daily meetings for updates and statuses. Kanban is less suited for smaller teams or groups who don't require collaboration and constant communication with involved users. Kanban is time-consuming and it takes additional effort outside of your regular work to maintain and manage the tool.
Read full review Pros Manageable workflow to ensure all users follow the same process. Can ban boards for easy visual of ticket status. Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model. Added communication tools help you get out of e-mail jail. Read full review It provides a good basic overview of where tasks are on a timeline (particularly helpful for a pull-based approach). It provides a good collaborative space to have multiple folks commenting on multiple tasks. It does a good job of managing very basic visual elements of an agile development cycle. Read full review Cons Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem). No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability. Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive. Request forms are very basic and there is no native dynamic field ability available. Read full review Kanban does not show the task or story clearly. You have to open the project separately to view the details of the project. Kanban gives a higher level project management view but it lacks customization and personal settings features. I would like to see Kanban provide mobile access to their tool, data, and board. This would be very useful for all companies and provide an increase in efficiency and productivity. Read full review Likelihood to Renew
We are more likely than not to renew our use of Kanban. Even with its limits, it still is a good product that fulfills our needs.
Read full review Usability
I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
Read full review
Again, this is a strong tool for software teams using Agile that are distributed across multiple geographies. It can be good for co-located teams too, but there are better platforms on the market like
that provide a more built-out story.
Read full review Support Rating
I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
Read full review
This is the best tool I had a chance to work with- since I started to use it I saved a lot of time and I made my work go smoothly.
Read full review Alternatives Considered
When I evaluated
, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did.
was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and
was the better option since it was less expensive and geared towards being a ticketing system.
Read full review
We've only tried JIRA Agile and KanbanFlow before. Kanban Tool was the one that our team actually liked and enjoyed working with. Also - it's been much easier to get started with and to understand than some of the other two (JIRA in particular). Although JIRA has many more features that we would have possibly used, the user feedback on it was so poor we were afraid that the negativity would create time wasted and less "job satisfaction" amongst the team.
Read full review Return on Investment JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people. Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool. Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well. Read full review Better communication and organization of ongoing projects. We are a very small team, with many areas to work on. Having everything in one system gives us a lot of visibility. Greatly reduced costs from using other tools that were much more expensive. Read full review ScreenShots Jira Service Management Screenshots