See PHI642. An install would like to give "Disable User" permission to all users so everyone can participate in a large "Battle Royale" event. This is an excellent idea but may justify shoring up some aspects of how user accounts are currently edited. This was "mostly done" in Week 33 by T13186.
See PHI757. Leaving inline comments on the right hand side of files not touched by diff B in an interdiff between A and B raises an error.
See PHI774, which discusses planning the pathway on T5953 and likely T3980. These are large tasks, but should be plannable today.
See PHI649. The file path typeahead in repositories can be difficult to use when your repository has a lot of long paths which all start with `/path/to/some/actual/directory/with/source/in/it/com/java/oracle/`.
See PHI580. An install would like write API access to object relationships (depends on, fixes, etc). This is complicated, but perhaps plannable, and we may be able to put a reasonable facade with partial support into the upstream. See some prior discussion in T13130. This didn't get much traction previously (see T13137) so the action may just be to punt it for now.
See PHI690. An install would like access to Drydock lease metrics, notably the time a lease spent in queue. See also T13073, but this is more narrowly scoped.
See PHI804, which encounters a confusion invite behavior on this install; possibly equivalent to T10071.
See PHI803, which notes that repository Tags (the Phabricator object, i.e. Projects) aren't visible anywhere reasonable.
See PHI802, which requests updated CircleCI support.
See PHI801, which may scope out into something else but has two stragglers ("Partial" sync status icon interacting poorly with inactive repositories; expanded Multimeter support).
See PHI838, which identifies a likely issue in hunk joining in Bundles.
See PHI836, which identifies a minor CSS layout issue.-----
See PHI811, which suggests swapping the default tab if the file tree is enabled. There are also a couple of scattered reports of file tree / mobile issues.// Fixed //
-----See PHI807, which touches on a documentation improvement about what `phd.taskmasters` does.
// Fixed //See PHI834, which reports a Mercurial 4.7 protocol issue.
See PHI807T13176, which touches on a documentation improvement about what `phd.taskmasters` doesthe "/new/" link in revisions shouldn't appear on the first mail.
See PHI834<https://discourse.phabricator-community.org/t/task-priority-change-info-missing-in-firehose-webhook/1832>, which reports a Mercurial 4.7 protocol issuequests "priority" transactions for tasks. These are likely trivial and "status" transactions are already supported.
See T13176PHI836, the "/new/" link in revisions shouldn't appear on the first mailwhich identifies a minor CSS layout issue.
See <https://discourse.phabricator-community.org/t/task-priority-change-info-missing-in-firehose-webhook/1832>PHI811, which requsuggests "priority" transactions for tasksswapping the default tab if the file tree is enabled. ThesThere are likely trivial and "status" transactions are already supportedalso a couple of scattered reports of file tree / mobile issues.