The "human workers need to do something nuanced" application within Phabricator.
First use case is customer support, including aggregating stuff from social media.
The "human workers need to do something nuanced" application within Phabricator.
First use case is customer support, including aggregating stuff from social media.
I think we're more-or-less at the point where the existing Nuance code is about as internally modernized as it's going to get, so there isn't a great deal of remaining obvious technical debt to pay down.
Ahh, makes sense now :)
In T12739#224605, @avivey wrote:Why is this Nuance and not Doorkeeper?
In T12739#224607, @chad wrote:GH Issues flow into Nuance and a human can decide whether to open it up as a Maniphest Task, similar to email. The end user can fully communicate an issue back to Phabricator without ever leaving their preferred source (email, Github, Twitter). Developers can stay in Phabricator and manage priorities, projects, workboards.
GH Issues flow into Nuance and a human can decide whether to open it up as a Maniphest Task, similar to email. The end user can fully communicate an issue back to Phabricator without ever leaving their preferred source (email, Github, Twitter). Developers can stay in Phabricator and manage priorities, projects, workboards.
Why is this Nuance and not Doorkeeper?
There's a typo in the headline, but I can't it :(