I took John Filicetti's suggestion at the User Conference to heart and added a number of custom fields to the Issues App to allow for Risks, Action Items, Changes and Decisions.  The fields added fine, but I find that I cannot control what the entry form looks like. 

It ends up a hodgepodge of fields all over the place.  I cannot organize the fields by Type or make any other cosmetic changes that would make this option useful to our users.

Is there functionality in PPM6 that I have not found that would let me sequence these fields (as I can for the Project Request) so they appear in a meaningful order or I can gather purely Risk fields separate from Change Request fields?

John,

I entered my fields in the order I wanted them to show up and then I used a bracket around the Initial for the type of form such as [R] for a Risk item.  Here are the UPDATED instructions, along with a view of my new form, and my new Issues view.  If you are using this solution or considering it, please take some time to look over the new document.  This really works and the Issues application shows up on your Dashboard and the Executive Issues view.  This view will also consolidate all items into one application if you ever consider creating a consolidated Status Report with Crystal Reports.

Hints: 

* The order you create your fields dictate their order on the form.

* I have started putting a "R-", "A-", "I-", "D-", or "C-" in front of the description so it shows up in the Dashboard and the Executive Issues view. 

John Filicetti:

I entered my fields in the order I wanted them to show up ...

John,

I looked over the document, but this doesn't appear to answer John's original question (which I have been struggling with as well). You entered the fields in a particular order, but the issues application places them seemlingly randomly throughout the form, for example data completed is the first custom field listed on the form, but it was your fourth or fifth field entered.

Mark

Has this field sequencing/layout issue been resolved?

Not to this point.  It is a concern through all applications, not just custom-creations.  There is some kind of logic behind it, but you have to play with the field list in a trial-and-error process to get the display the way you want.