@Mariam Paronyan , I love all the suggestions on this thread and would love to participate in any beta opportunities in the future. I especially like the suggestions to combine overview and custom forms into a single view, determine the order that they appear, and the ability to have forms and sections in forms to appear collapsed or expanded! Like someone suggested I think it is important to have the ability to be flexible with the application of these settings because not all projects are the same and some data is more important than others depending on the project. I would like your feedback on my earlier comment related to having the ability to assign "default" forms that should automatically be attached to a project for any new Task or Issue that is added. This would be a dream come true for us for two reasons: 1) Me and the other system admin had to spend a lot of time monitoring exception reports to ensure that PMs have attached forms (depending on the project) to the new Tasks/Issues that they add. If we could automatically assign default forms to each project, for each of these objects, this would help reduce the amount of time we spend on this. 2) We have views for PMs that use fields from our custom forms, if the PM populates this field using in-line edit functionality and a form was not already attached to that Task/Issue, Workfront automatically attaches one. It seems to pull the first form ever created that utilizes that field. For us, in most cases it is the wrong form, because there are several forms that we no longer use, but cannot delete from the system because we would lose data on older items. This also results in more work on our side to identify these and correct them. In respect to forms in general, it would be nice if we had a separate attribute on every field we create to have a "label" to indicate how we want the field to appear in list, chart, and matrix reports, etc. that is different than the name that is the actual field name. Again, change drives this requirement. Sometimes we have created fields that are a little more descriptive of what it should be, however, that doesn't always play well on a form, especially it we make a minor tweak. For instance, our department used to be named MIS (Management Information Systems) and was renamed a year ago to ET (Enterprise Technologies). Some fields that we created that were specific for our department and were named to also indicate ownership of the field for anyone who was using the form. For instance, our MIS Review field. This field is used in a lot of places, filters, views, reports, etc. both in builder and text mode code. We need to rename this field ET Review, however, we don't have the ability to easily accomplish this without creating a negative, cascading effect on everything that uses it. Something that should be a simple change turns into a major project to accomplish. Additionally, it's not always easy to find every location in Workfront this field is in use in standard and text mode code. Do you know if there are any improvements in this area? Admin Kelly-Wehrmann SSFCU