Coming here from thinking more about T253744: Improve initial Phab task quality: Encourage use of bug report/feature request task subtypes; Review default options in Favorites menu and how to "encourage" setting task subtypes.
Phabricator introduced Forms ~4y ago (in addition to passing URL parameters), in order to create tasks / prefill data in the task creation form.
Since then we've seen a growing number of Phab forms created.
We currently seem to happily create forms to cover specific use cases, but some forms don't seem very discoverable if you don't know about them.
Plus we have no idea which forms are actually used and which once might not be used anymore, as there is no way to find out which task was created by using which form.
Plus some might overlap (or superseded by others without disabling the older ones, and the older ones still linked from somewhere).
I'm wondering if having access to HTTP referer logs and analyzing them could help.
I don't know if this is feasible at all, or if my use case makes enough sense.
Input welcome.