I think 'only email certain people on certain cases' for audit is covered by T2497. T5889 might also be of interest if you are trying to do herald rules with Audits.

@JohnTheodore Phacility offers paid prioritization which sounds like what you are looking for. See T4778 for general comments on when upstream will do X.

For the import use case custom fields already have an edit boolean which might get you most of the way there.

@cpa199 it sounds like you want T4427

I like the idea of a policy option to let me unleash excessively attentive people on our install to keep it clean without giving every user a way to mess things up.

I got some some similar feedback which I would summarize as "reduce
number of actions needed to create a new task".

Is that you can't search for Maniphest:Backlog or you can't search for *:Backlog.

I presume per column scrolling would change this behavior, but right now if there is a single long list I end up with double vertical scrollbars and can't use pagedown/down-arrow etc until I click somewhere.

All comments, and then some actions (adding a CC, resigning) but not Accepted.

Not sure if this is new, but with HEAD toggling 'ignore' on a setup issue triggers a setup issue for 'Phabricator Daemons Need Restarting'.

One particularly specific request came up: "I want to get email when a commit is Accepted only if there is a comment"

It's entirely possible -- reasonable even -- that the 'Request Review' action will kick this out of 'Needs Revision'.

Narrowly what some people have told me is is that the flow with the back button(s) to get the the "next" audit is annoying. I think if I've read it right that's what Chad's "work through a queue" description is trying to address.

Nope, just hanging out and following interesting looking tickets before our next upgrade.

• break long line

Nothing is broken per se, it's just confusing people. Some are interpreting it to mean "I fixed the problem" in response to someone raising a concern.

In T5928#6, @chad wrote:

Oh I see, you don't even want Accept as an option, regardless of if it doesn't close or not?

Not sure what the right button to press is to get this out of 'Needs Revision' now that the document is signed.

For giggles I applied the patch instead of following the test plan and we didn't die on a for loop.

Hmm so with master + this patch I see 'Cacheable: Yes' , but image urls still 404 if not logged in.

Not sure what the convention is for logging in daemons, but should this get a log message instead of silent bail?

Even better.

It looks like something to do with {meme, src=foo} vs just foo

Somewhat related: T5550

I'm currently evaluating using Phabricator and this is one of the areas that is tripping me up. We have >100 internal git repositories. In theory they are all lower-case-with-dashes, but some camelCase and underscores have crept in. Trying to create short memorable callsigns for all of them isn't going to work well for all the obvious reasons, and search-service-dropwizard.git-->SEARCHSERVICEDROPWIZARD is ugly and will run into all of the same limited space problems described above. We are used to trac with has many ways to link to things, but honestly linking to commits has become less common since we switched to git (and it got more complicated than r123).

Thanks! Will try to integrate it out as I continue our proof of concept.