I've found that phabricator seems to lack support for more complicated workflows so you end up having to hack together things using tags/workboards/milestones to mirror how your process works. This could be a positive though if you've suffered through really crappily configured JIRA projects.
To phab's credit, the web UX of phab is more respectful than JIRA (10 second load times anyone? constantly (re)moving things) but I've used go-jira[1] for the past 2 years to great effect and there's simply no equivalent of that for phab.
It could also be that I'm just stuck in my habits and don't like change - or the way my current orgs phab install is configured (I've never been a JIRA or phab administrator so I don't have much insight here)
To phab's credit, the web UX of phab is more respectful than JIRA (10 second load times anyone? constantly (re)moving things) but I've used go-jira[1] for the past 2 years to great effect and there's simply no equivalent of that for phab.
It could also be that I'm just stuck in my habits and don't like change - or the way my current orgs phab install is configured (I've never been a JIRA or phab administrator so I don't have much insight here)
1 - https://github.com/go-jira/jira