What is the challenge?
The new Aha! Roadmaps features board includes record-type options that some teams do not use.
Administrators cannot find a navigation setting to hide these unused options.
What is the impact?
Showing unused record types can confuse users
Describe your idea.
Allow administrators to hide unused record-type options, including requirements, on the new features board.
Apply the configuration for everyone in the workspace so the board reflects the team's process.
You can now hide the requirements toggle on the new features board. Open Customize view using the gear icon and select Hide requirements to simplify the board for teams that do not use requirements.
This update specifically supports hiding requirements, not every record type. It does not disable requirements or change access to them elsewhere in Aha! Roadmaps.
The new features board introduced an additional ticket layer, requirements, which is creating confusion for users who may not know whether to create a requirement, feature, or epic.
We did not anticipate this change affecting our portfolio management process. The update disrupts how our teams manage work and creates challenges for consistency, adoption, and reporting.
We need Aha! to provide a UI toggle to disable requirements as soon as possible so our teams can continue using the issue types and workflows that support our portfolio management model.