how dynamic do you want that text?
How many different options are you thinking of?
Too dynamic and you might as well leave it blank (no default text) and just make sure BG_DESCRIPTION is mandatory.
How would you determine what the dynamic text should be?
Would you want to use an InputBox or a MsgBox or try and trigger different values depending on where the user raises the defect from (i.e. from a run, or not) ..?
Hmm.... You have such a lazy QA... [img]/images/graemlins/smile.gif[/img]
It doesn't make sence, because it will be necessary to create very complicate script, becuse HTR is not only information that is writing to the memo pole. And you have only this now, it's possible that after few monthes this rules will be changed.
Complicate because you should handle <Enter> pressing only for HTR cases, but user could divide by new lines some special blocks of information, like OS version, or some note about additional stuff, or even expectation/actual info.
Thus you'll spend a lot of time for writing this script instead of teching of your QA "how to press symbol '2' on the keyboard".
And for the last, QC memo fields (QC 10 and earlier) doesn't contain engine for script parsing/running. There's only html parsing there.