When comparing ProofHub vs JIRA Agile, the Slant community recommends JIRA Agile for most people. In the question“What are the best project management tools?” JIRA Agile is ranked 18th while ProofHub is ranked 28th. The most important reason people chose JIRA Agile is:
You can provide custom workflows for all the different types of issues. For example you can make features go through a flow of "Backlog -> Needs design -> Built -> Needs QA -> done" with bugs going through a different flow. These workflows are very powerful as you can configure them to automatically assign your QA lead when moved into the needs QA state. These features do require some learning curve to set up, but make the tool a lot more efficient to use as things like managing who is assigned to an issue can be automated.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extensive customer support
A knowledge base is provided in their site for FAQs, use cases, and video tutorials. In most cases, the answers you are looking for are already addressed in this section.
The website also provides an Update Page to keep you informed about the latest features or issues about the software.
Their Facebook page and Twitter handle are active and responsive. You can communicate with them via their social networks.
Pro It has great Gantt charts, personal views, project separation, user roles, different ways of presenting information, bulk upload, templates, etc
Pro Easy to use
Functions and tools are straightforward and intuitive for a non-technical user.
Pro 5 pricing plans that should fit anyone's needs
There are five different pricing plans for ProofHub, including a free plan, making for a flexable structure in which users can find the plan they need without spending over what they want.
Pro Highly customisable and powerful workflows
You can provide custom workflows for all the different types of issues. For example you can make features go through a flow of "Backlog -> Needs design -> Built -> Needs QA -> done" with bugs going through a different flow. These workflows are very powerful as you can configure them to automatically assign your QA lead when moved into the needs QA state. These features do require some learning curve to set up, but make the tool a lot more efficient to use as things like managing who is assigned to an issue can be automated.
Pro Powerful tools for issue management
Issues in a current sprint are viewed in a Kanban interface. But for the issues not in a sprint Jira provides a compact view with many powerful tools to search and filter the list. You can create custom filters such as "Show me all issues not yet designed that are assigned to me" and a variety of other tools that make dealing with large backlogs easy.
Pro Has App Marketplace for extensions
Pro Helps you focus on what's important
Jira is a truly Agile software as you may concentrate on the active sprint and the tasks you have to do.
Cons
Con Slow to use
Every view switch and action takes a second or two. Doesn't seem too bad when you first start using it, but the UI is complicated enough that you need to manipulate it a lot and all that time adds up.
Con Merely a thin interface to a massive database
Too many configuration details, too confusing, too difficult to search and modify numerous tickets.
Con Email defaults are crazy-bad
The default is seemingly to email everyone on the team every change on every ticket. Which is stupid-bad. It means you get spammed with so much JIRA garbage you miss actual message tagged with your name.
Con Terrible editors barely work
The in-page editor for issues have lots of issues, plus several hacked-together features that barely work with each other. It's nice that you can drag and drop an image, but just try to format inline text as code, or block text as code, or to use the styles, and you'll find several places where things just FAIL.
Con Expensive
User based price model
Con Ancient
Non-reactive interface.