See T13096. An install is experiencing a cluster synchronization issue on one node, but the immediate symptom is a held lock.
See PHI410. See PHI348. Multiple installs would like API access to the commit which closes a revision.
See PHI417. An install would like to contextualize the "landed irresponsibly" stories from feed. (I plan to just hide these, there's just a bit of a technical trick which makes it non-trivial.)
Entering MFA credentials during an OAuth server redirect workflow can currently be blocked by the CSP.
See T13100. See `support@` email thread about being unable to edit a revision. This is PCRE shenanigans.
See PHI423. An install would like T11015 fixed properly. PHI254 also touches on this.
See PHI424. Another install would like T11664 and I think we have enough interest in this now to just bite the bullet.
It would be nice to fix T12590 alongside the other Owners changes.
See T13101. See <https://discourse.phabricator-community.org/t/meme-remarkup-tag-no-longer-working-after-upgrading-to-2018-w09/1210>. The `{meme ...}` Remarkup composer currently violates the Content-Security-Policy if a CDN domain is configured. The `{img ...}` imageproxy rule also violates the Content-Security-Policy for similar reasons. See also PHI437, sort of.
See PHI427. An install would like a way to render a short Doorkeeper external object reference. Update: this is hard because Doorkeeper uses the remote object reference as a cache key in both client and server workflows, and can't currently distinguish between different views of the same object. Not insurmountable but should actually get proper testing.
See PHI432. An install would like to query repositories by short name.
See PHI434. The "Strip MFA" workflow in the cluster doesn't properly dirty the user enrollment cache. This is a Phacility-specific issue with our instance management toolset.
See PHI433. An install would like to improve some of the messaging around drafts.
See PHI431. An install would like to support a nuanced workflow in review actions that probably doesn't make sense as a default upstream workflow but may mesh with T731 and which we may be able to provide some support for.