[Feature Request] Support "Wrap Text" toggle for columns in Projects Table View

[ihor-liehotin-ihli]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Projects

Body

Problem Statement:

In the current GitHub Projects Table view, "Text" field types (and long "Title" fields) do not support text wrapping. When content exceeds the column width, it is truncated with an ellipsis (...). This makes it impossible to scan important context — such as QA notes, status updates, or technical summaries — without manually opening every single item or hovering over cells.

Version Context

This request applies specifically to the new GitHub Projects (v2). This is not a request for "Projects Classic." The issue specifically concerns how the new Table layout handles custom Text fields and long titles.

Why this matters:

• Reduced Efficiency: It breaks the "spreadsheet" workflow where users expect to see all data at a glance.
• Context Loss: In fast-moving triage or stand-up meetings, the "hidden" text causes team members to miss critical details.
• Inconsistency: Other similar tools (Notion, Airtable, Excel) provide a "Wrap Text" or "Row Height" setting as a standard feature.

Proposed Solution:

Introduce a column-level setting (similar to "Filter" or "Sort") that allows users to toggle "Wrap Text" on or off.

• If OFF: Keep the current behavior (single line, truncation).
• If ON: Allow the row height to expand dynamically to fit the text content within that column's width.

Visual Example of the problem:

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐