Hi John,

> I have updated the IssueClass section of the docs to read:
[...]
> Is that sufficient?

Yes, thank you. Those doc changes are very welcome, and would probably
have put us in the right direction from the start.

That being said, try_id_parsing='no' may be a poor fit for us. We use the
REST API heavily for our customer portal, which searches and updates
user links (e.g. contacts on a custom class) by user ID. From Ralf's
description, it sounds like those IDs could then be read as usernames,
and a class-bound switch would presumably have the same effect.

This could naturally be handled in the portal, but that's not something 
you pull off in an afternoon ;)

> Ralf, what are your thoughts on including something like this in the
> default auditor?
> By default it would add an alphabetic suffix (a,b,c,d...aa, ab...)
> to any pure numeric username.

The auditor approach looks like the safer solution for us, so we'll
add it to our own user auditor for now.