I had a look at Phabricator. As a developer-noob I might be using improper terminology in the following, or might just not have sufficiently familiarized myself with Phabricator, so set me right if either of those possibilities is the case.
It seems to be a developer-facing app, rather than a user-facing app. That is, what constitutes a “task” is what the developers decide is something to do. Before they decide, the thing is either a bug or a wished-for feature. After they decide it will be worked on, it’s all one thing: a task.
That distinction was brought home to me recently when I went to the bug-tracking site of a popular software package and logged what I thought was a bug. It was explained to me that it was actually the geekish way the software is supposed to work (using geek logic rather than human logic) and therefore not a bug, and the bug entry was therefore marked as closed. I considered arguing that the software’s behaviour was a desirable thing to change, but thought better of it, because, after all, I was on a bug-tracking site and my comment would be inappropriate in that context. It would probably be recommended that I state my case on a forum on another site where they have a subsection for feature requests. But the developers might not bother to ever look there. Hmmm.
So, what I would like to see is a tracking system that neatly keeps bugs and feature requests separate, but in which an entry can be conveniently moved from one category to the other. Can Phabricator do that, or am I overlooking the obvious?