The default home page (and homepage sidebar notification count) are also still doing the old grouping / counts. We should probably fix that but it's not a strict dependency here and there's adjacent work (T3583).

Yes, since it would really mean exact(current-viewer) without additional work. Are you using it for something (dashboards?)

I'm no longer able to search for "Responsible Users: (Current Viewer)". Is that expected?

Bucketing is now controlled by a "Bucket: ..." option in the search query controls instead of hardcoded as a behavior of the "Active Revisions" filter. This means that you can apply bucketing to other queries. You can also extend DifferentialRevisionResultBucket to implement your own bucketing algorithms (but: here be dragons).

I'm going to merge this into T10939, which answers this question in practice if not in theory.

There are now six buckets which are more action oriented (Must Review, Ready to Review, Ready to Land, Ready to Update, Waiting on Review, Waiting on Authors) and bucketing is more flexible.

In T9263#175460, @epriestley wrote:

(The slightly more intuitive "Reviewers: SomeProjectName" will also work.)

D15930 adds an icon hint for this that looks like this:

(You can create an oldest-first dashboard yourself now if you prefer the old ordering, and can probably force it on all users after T4103 if you really want.)

This also indirectly flipped the ordering from oldest-first to newest-first. I'm inclined to retain that ordering, since it's consistent with every other application. The "oldest-first" ordering was a sort of paternalistic attempt to force users to review stuff, but I think we've generally moved the software away from that a bit and it doesn't feel very much at home to me any more.

+1 for iframe syntax - don't need google docs but we've been wishing that we could embed iframes into our phab diff summaries.

I pushed that stuff live but bucketing has some bugs, looking into it.

thanks! Will try it out when we update here. @angie can you ping me once we update to this version on our side?

Not sure if this should be another bug report but the / that is added at the end causes issue when using anchor tags i.e if [[ ../2016.19#gotolocation ]] was the markup the link would also be broken by adding a / at the end.

(The slightly more intuitive "Reviewers: SomeProjectName" will also work.)

I have marked D15925 as fixing this. T10939 has some broader discussion. This isn't an exact fix for the original request, but I suspect it may be close enough to be satisfactory.

This is almost definitely T8298, because % can't be properly escaped on Windows right now.

This specific issue also happens on my computer, which is running Windows 7 SP1 with PHP 5.6.20

Collecting some additional dashboard cases from stuff merged into T4144:

cslint is deprecated, see T8978.

Closing this because beyond diagnosing initial configuration, there isn't much value in making things this much more complicated.

cslint is deprecated, see T8978 for more information.

We're no longer (at work) planning or intending on continuing use for EC2 blueprints. If there's anyone else out there that wants this functionality, feel free to re-open this task.

We're no longer (at work) planning or intending on continuing use for EC2 blueprints. If there's anyone else out there that wants this functionality, feel free to re-open this task.

It's not email client dependent - Phabricator is writing out the wrong URL when sending email.

Which email client is this about?

Packages can now be reviewers. They work very similarly to project reviewers. They can be added via the web UI or Herald. They can also be added via the CLI (by typing O123 as a reviewer or subscriber) but this isn't very convenient and I don't expect users to manually add them very often / ever.

Archived packages are no longer added as auditors to new commits after D15907 by the "Auditing Enabled" setting.

I run into this problem a lot because workboards doesn't support custom forms yet :(

Beat me to it :P

Oh, I see I already made that suggestion! I am nothing if not consistent.

In the meantime, we could maybe do the following: