Login Verification to Applicable Support Catagories
Short, concise description of the idea
Certain support categories, where appropriate, should require the user to login for the question to be posted.
Full description of the idea
Catagories such as Customization, User Picture Icons, Communities, Embedding, and Client:Web are much more accurately answered and answered in a more timely fashion if the user marks that they are a Live Journal user and enters their username and password in the appropriate fields on the /submit.bml page.
And a Possible Part II: a category solely for non-users of LiveJournal which would enable all the other categories to require the user enter their username and password.
An ordered list of benefits
Requestors wouldn't have to wait for someone with the appropriate priveledges to post a comment ask for the user to log in, or other fact finding questions, and then wait until after the requestor submitted the information for someone to answer their request
In some cases it will make the user post the question in the appropriate catagory
Even in cases where the user doesn't necessarily need to be logged in, Support Volunteers with have more data to work with when trying to answer a request, thereby increasing the accuracy of the answers.
An ordered list of problems/issues involved
Have no idea what the coding would be like on this on, or if its even possible to require validation of Username/Password field on some instances of a Drop Down menu.
If only some categories required this validation, a user might just post to the wrong category in an effort to get their question submitted, which would lead to a priv eventually moving the request.
An organized list, or a few short paragraphs detailing suggestions for implementation
If the sort of validation I'm refering to isn't possible from a Drop Down menu, then perhaps the category fields could be moved and duplicated, one beside the Yes, Live Journal user radio option and one beside the No, Non-User radio, each containing appropriate Catagories.
Both would contain the General/Unknown category, but if selected from the "Yes" option would require login, from "No" option, would not require login.
An error page would need to be created, in place of the confirmation page when the user didn't include login when required, Detailing what information needs to be corrected before the answer will submit.
If the validation I'm referring to can be accomplished with a the existing Drop Down menu, then after it is set in place the only other step that I know of would be to create a custom error page, as mentioned above.