I have seen something similar in a presentation from an HP consultant. It was used to describe what the RT was meant to be used for. I think it was a text area as the first field in the header with HTML content (read-only) that probably was only visible in the "not submitted" state. It seems to be a good supplementary help text in addition to the usual field help. If you go for editable, you will probably have to live without HTML formatting.
It has been a customized request header. Most likely he added a custom field of type text area to it, gave it field prompt like "Hint:" and then added whatever text should be displayed in HTML format as constant default value for it. Then make it visible for status "not submitted" and no other status (and optionally readonly in general). Please have a look at the attachment. Instead of using a constant default, you could also use a rule that populates the field and have the rule fire on page load. This way you could use the same text area with different texts for different statuses.
Hi, I frequently use the technique Sascha is talking about. Though I dont recommend populating the text area with rules as the formatting gets all messed up. Use a constant. You dont need HTML formatting, I dont even think HTML is interpreted. Just put the text as you want it to show to the user. Johan
you can put a custom token where you store notes mesaages in either request detail or header, then set display notes history attribute = true, in request creation process, set the first step to be an execution step where you set your custom token. After that the change in yoru custom token will be added to notes section.