Preserve and Apply Manual or Smart Automatic Column Resizing for Embedded Report Views in Aha! Documents

Aha! currently allows users to manually resize columns while viewing a report list view, which is extremely helpful for making large text columns readable and minimizing wasted space for short fields like IDs or statuses. However, when these reports are embedded as Aha! views within notes or documents, the custom column widths are not retained or respected—resulting in poor readability, truncated content, and inefficient use of space.

Problem:

• While viewing a report in Aha!, users can drag to resize columns and optimize the display space for that report needs.

• When embedding that same report as an Aha! view (e.g., in a document or note), the column widths revert to automatic sizing, often making large text fields unreadable and causing unnecessary wrapping or truncation. All columns are equal sizes.

• This breaks the continuity between report configuration and how reports are presented in documentation or shared executive summaries, which diminishes the value of embedding dynamic custom reports. as part of the larger document / note

• Breaks consistency between the report view and its embedded presentation in Aha! documents, leading to confusion for stakeholders who expect formatting to remain the same across contexts.

• Causes critical content - such as detailed descriptions, notes, or commentary - to become elongated and hidden under scrolling space, making reports significantly less readable when embedded in planning documents, business cases, PRD's and executive summaries.

• Requires manual workarounds, such as screenshots, just to achieve basic readability and presentation for larger audiences.

• Reduces the perceived professionalism and effectiveness of shared reports, especially for leadership, internal stakholders and customer-facing communication.

• Wastes time and increases user frustration, as report creators must reformat or explain missing/truncated data to reviewers and decision-makers.

• Discourages leveraging Aha! documents and embedded views for centralized, single-source-of-truth reporting, reducing adoption and collaboration efficiency.

• Impedes the ability to use Aha! documents as living artifacts for quarterly planning, retrospectives, and ongoing project management, since the embedded data does not reflect the original intent due to having to screenshot items.

• Ensure that column widths (Percent of total width) set by the user when viewing a report are preserved when that report is embedded in an Aha! document or note as an Aha! view.

• Alternatively, allow users to adjust column widths for embedded notes, and have these respected ifor that document specifically.

• Improve auto-sizing logic so that embedded reports more accurately reflect user-set column sizes or the actual content length, if persistence is not feasible.