Problem: When reports about production issues are opened on WMF projects, it is difficult for those reporting the issue to know when the production issue is purportedly resolved.
Proposed solution: Expand the use case for Phabricator to include incidents and problem, instead of only tasks for solutions.
Who would benefit: Users
More comments: Phabricator states are really only used to indicate that software changes have been created merged, not that they have actually been deployed. People with issues are generally trying to open "incident reports" - not "software requests" - they are telling a user story, but their story doesn't end until the situation is no longer presenting to them.
