Page MenuHomePhabricator

Obtaining Phabricator version should not require administrative permissions
Closed, WontfixPublic


Repro steps

  1. Log in at
  2. Go to
  3. Get 403 forbidden screen

I'm a pretty active user on this install. It seems strange to hide the version information from logged in users, especially when a requirement of reporting bugs is the Phabricator version

Event Timeline

chad added a subscriber: chad.

I'd say 75% or more bug reports we get require administrative access to resolve. You can spin up a Phacility instance for free.

chad triaged this task as Wishlist priority.Nov 21 2016, 9:47 PM

Basically anything that would be accepted as a Bug would require you to have admin access to some install before you have enough information to submit it, so this is more-or-less a moot point.

epriestley claimed this task.
epriestley added a subscriber: epriestley.

WMF has extensions and modifications to Phabricator so you shouldn't report anything you experience on that install to us directly. Report it locally, make sure it isn't because of an extension, then bring it upstream. The versions we could show you would not be useful anyway because they'd be hashes of local commits which do not appear in the upstream, so we would just close your report as invalid and say "test with unforked code before submitting a report" anyway.

If you observe a bug on WMF, you can test on a clean test install on Phacility for free in a couple of minutes and obtain versions there.