The Wikimedia Foundation adopted Phabricator as our developer collaboration platform. This project organizes our feedback upstream.
https://phabricator.wikimedia.org and https://www.mediawiki.org/wiki/Phabricator
The Wikimedia Foundation adopted Phabricator as our developer collaboration platform. This project organizes our feedback upstream.
https://phabricator.wikimedia.org and https://www.mediawiki.org/wiki/Phabricator
I'm going to merge this into T12738. Although that task primarily discusses Nuance as a Phacility support tool and we ended up building a standalone Support tool instead, I generally believe Nuance is the most likely pathway for interactions falling under the general "helpdesk" umbrella.
This isn't an actionable task. It covers too much ground, describes too many features, and most of it lacks compelling use cases.
No plan to continue on this?
This is intended and has legitimate use cases.
In T8510#200946, @aklapper wrote:In https://phabricator.wikimedia.org/T76732#2803813 ksmith brings up that "In the search bar in the toolbar at the top of the screen, searching for "Maps" brings up Maps as the third option. Searching for "Discovery" brings up Discovery as the second option."
After D19384, we'll automatically mark these "phantom" notifications as read when you open the menu to review them:
This will ultimately be covered by T13105.
See followup in T13105.
Also relevant:
(For completeness, this came up via the support queue in PHI411.)
This task is a giant mess with pretty much no remaining actionable use cases. See T13074 for plans. If you want some use case here included in that, file a description of your problem via support pact.
I second this:
Not all applications have full policy support yet, usually because it's blocked by something or they're beta.