Customize the Requirements View under Feature Custom Layout
I would like to be able to add the Story Point estimate so that you can see at a glance how large each story is without having to click on the story to open it up. (see screenshot)
Feature & Requi...
Feature & Requirement Customization.jpg
Open full size
Feature & Requirement Customization.jpg
Guest
Dec 23, 2025
What is the challenge? Currently, the Requirement/Story tab under the custom layout for Features/Epics is not editable. This limitation prevents teams from customizing the view to meet their planning needs.
What is the impact? Because the tab cannot be modified, we are unable to add an additional custom field next to Status. This field—Sprint Name—is critical for sprint planning and prioritization. Without it, teams lack quick visibility into sprint allocation, making prioritization and planning less efficient.
Describe your idea Allow editing of the Requirement/Story tab in custom layouts for feature so teams can add custom fields (such as Sprint Name or any other) next to Status. This enhancement would significantly improve sprint planning, prioritization, and day-to-day workflow visibility.
Or generally, allow customization of the layout of the Requirements view, just as we can customize the Overview tab. For our use case, we would love to display the integration ID instead of the Aha Requirement ID.
What is the challenge?
Currently, the Requirement/Story tab under the custom layout for Features/Epics is not editable. This limitation prevents teams from customizing the view to meet their planning needs.
What is the impact?
Because the tab cannot be modified, we are unable to add an additional custom field next to Status. This field—Sprint Name—is critical for sprint planning and prioritization. Without it, teams lack quick visibility into sprint allocation, making prioritization and planning less efficient.
Describe your idea
Allow editing of the Requirement/Story tab in custom layouts for feature so teams can add custom fields (such as Sprint Name or any other) next to Status. This enhancement would significantly improve sprint planning, prioritization, and day-to-day workflow visibility.
Or generally, allow customization of the layout of the Requirements view, just as we can customize the Overview tab. For our use case, we would love to display the integration ID instead of the Aha Requirement ID.