I'm sorry, Derrick, but I don't quite follow you here. The Issues keyword is valid for any of the following contexts:
Top level, use case, actor, requirement, diagram, dictionary, test scenario, package
Since issues can be owned by either use cases or definitions directly, there's not a DomainObject keyword necessary - just use "Issues" with a list keyword (like $repeatIssues or $listIssues) in the context of your use case or definition to grab the issues and any properties you'd like to report on.
I suspect I might be missing the boat on this one, though. If you need more help with this, send an email to us at support@serlio.com with some samples and additional details illustrating what you're looking for and we'll give you a hand.