Program admins can arrange the requirement detail page into sections for their program. Everyone in the program sees the same layout on the requirement detail page and in the edit form.
Open the layout editor
Requirement Layout is available to people who can edit the program, once the program page is enabled for your workspace. Use either route:
On the requirements page, open the program selector.
Choose `Requirement Layout`. The editor opens in a side panel next to a preview.
You can also open the Layout tab on the program page. The program selector menu also has Program Settings, which opens the program's settings without leaving the requirements page.
Arrange sections and fields
In the editor you can:
Give each section a title. A section needs a title, and leading or trailing spaces are removed.
Move fields up or down, or into another section.
Hide built-in fields you do not use.
Place the program's custom fields among the built-in ones.
Select Save layout to apply your changes to the program. The button stays disabled until you change something.
Name, Status, and Statement always show. If you remove them from the layout, they return at the top of the first section.
Closing the editor with unsaved changes asks you to confirm before it discards them.
Fields you add later
A custom field that is not placed in the layout appears in the More fields section. If the layout has no such section, the field goes into the last section that is not Permissions. The same applies to a built-in field that becomes visible again after its access was restored.
A custom field the program hides keeps its place in the layout. When you unhide it, it returns to its old section.
Reset to default
Select Reset to default and confirm with Reset to remove the program's own layout. The program then uses the layout inherited from its base program, or the default layout if there is none.
Shared programs and clones
A shared program uses its base program's layout until it saves one of its own. Fields from the base program that the shared program cannot see are left out, along with sections that would only contain them. The shared program's own custom fields appear in a trailing section named after the program.
Cloning a program copies its layout and points it at the cloned custom fields.