Include demographic validation fields (ie Gender) in URL
closed
J
John Campbell
So the valid options in customer facing software, be it SaaS, Enterprise, or whatever are to: ask questions to get a better understanding of the customer's request if not well understood, reply with a reasoning about why the FR doesn't fit the product giving the client time to reply why it should be implemented, close as duplicate. Even volunteer contributors of open source projects on git don't just close things out without thoughtful interaction with the requester. Unilateral unexplained closure of an opened issue/FR doesn't really exist. This is surprising and disappointing considering how long the issues were open without response and how long i've been a client.
Issues closed without reply:
-Include demographic validation fields (ie Gender) in URL
-Increase gender demographic validation to include option to immediately route user out of study if they get their gender wrong
-Block VPNs
-increase Website Login Timeout
-Include more demographics alongside gender in demographic verification/consistency
Shimmy Krumholtz
closed