In general, we don't offer consulting/contracting services, and only want to add code to the upstream if we believe it will be broadly useful across organizations and use cases (since we have to maintain it going forward). To the degree that you have detailed requirements specific to your workflow, the most direct way to get the features you want built might be to fork Phabricator and hire a contractor to build the features (we don't have any great referrals, unfortunately).

If you want to work with the upstream, we do offer paid prioritization of features, but try pretty hard to limit this to things we'd want to put on our roadmap anyway. Often, this breaks down as having fairly good (but not perfect) overlap with what you want. Depending on how good this overlap is, you might be able to find some reasonable workflow compromise on the rest of the features, or develop extensions in house or by hiring a contractor.

In this case, it looks like Custom Fields can already do most of what you want. Have you looked at them? Here's a screenshot of a bunch of custom fields on my local install to give you a sense of how they work:

Particularly, you should be able to add Type, Stage, Due Date, Estimate and Work Done using custom fields. Custom fields are filterable and editable. You can find Custom Field documentation here: https://secure.phabricator.com/book/phabricator/article/custom_fields/

So I'd suggest:

• Figure out how close you can get to what you want by using Custom Fields.
• Let us know what's still missing, or what you can't figure out how to do. I think you should be able to do almost everything you want already.
• Based on that, we can determine how to move forward. For example:
  • If you need general behaviors, they might be reasonable upstream features.
  • If you need highly specific UI, Custom Fields are reasonably easy to extend locally.

For the other items:

• Triage Tool: You should already be able to use Maniphest search to filter to any set of tasks, so "condensed and editable" is probably the key here. Particularly, after adding custom fields, you can save a query which shows tasks with type "Product Request" in the "Needs Triage" state. I'm not immediately sure what you mean by "condensed and editable", or exactly what you're envisioning.
• Time Tracking View: We have a very beta application called Phrequent which does time tracking, but improving it to a useful level is probably a large amount of work. As described, this probably doesn't fit very well into our broader vision and might be better built locally. I can build you a 5-minute version when we get there.
• Subtasks: See discussion in T4207.
• Swim Lanes: As described, this probably doesn't fit well into our broader vision. Have you looked at Workboards? They're significantly different from what you describe, but might be close enough that they could serve as a starting point:

In general, philosophically, Phabricator is not a high-process tool. Although we think we can improve it significantly as a project management tool, we don't envision it ever having the same level of sophistication, customization, user-definable workflows or detailed reporting that a tool like JIRA has. If you haven't already, it may be worth evaluating other tools (like JIRA) to see if they fit your requirements better without additional work. JIRA also has a far richer consulting ecosystem than we do.

Thanks for the great info for us to start with. We'll further evaluate current needs and keep this ticket open for continued discussion.

Sounds good, let me know if we can answer further questions as they come up.