We’re currently testing the Custom Fields by Task Type beta and really like the concept. However, we’ve run into an important limitation that strongly impacts day-to-day usability and reporting: At the moment, Custom Fields created per Task Type do not appear in List or Board views, nor can they be enabled as columns or shown on board cards — unlike standard workspace custom fields. This creates a gap between: Contextual work inside the task (where Task Type fields work very well), and Overview and management views (List / Board), where those same fields are often essential. Why this matters: In real-world setups, especially in multidisciplinary teams (design, development, QA, training, meetings), Task Types are ideal for defining which fields matter — but teams still need: To see key Task Type fields at a glance in List or Board views To use them for filtering, grouping, and prioritization To avoid duplicating critical fields as global custom fields just for visibility It would be extremely valuable to allow: Task Type Custom Fields to be enabled as columns in List view Task Type Custom Fields to be shown on Board cards (Ideally) Task Type Custom Fields to be available in filters and views, scoped to tasks of that type This would fully unlock the potential of Task Types as structured, context-aware task models — without sacrificing visibility or reporting.