Capture custom project data once and use it everywhere.

What sets Project Insight's custom fields apart?

Most work management tools let teams add columns to a task or a board. Project Insight treats custom data as project data: it lives on the native records a PMO runs on, follows a request into the project it becomes, and shows up in reports, dashboards, and portfolio roll-ups without being rebuilt anywhere.

• Capture once at intake: Matching custom values on an approved project request prepopulate the project created from it, so nothing is re-keyed.
• Reach the portfolio: Decide per field whether it can be displayed, filtered, grouped, or totaled, then use it in project, program, and portfolio reporting.
• Cover the whole record set: Add fields to projects, tasks, issues, requests, users, companies, and nearly every other Project Insight record.
• Create new business records: Build assignable custom items with their own naming, numbering, attachments, client visibility, and reports.
• Collect structured data: Use table grids, signatures, dependent lists, and built-in selectors for users, companies, departments, and groups.
• Protect sensitive values: Treat a project or task custom field as financial data so it follows Project Insight's financial visibility rules.

Key custom fields capabilities compared across Project Insight, monday.com, Asana, Smartsheet, Jira, and ClickUp.

Key Custom Fields Capability	Project Insight	monday.com	Asana	Smartsheet	Jira	ClickUp
Request data carries into the approved project	Yes: Matching fields prepopulate when the request creates a project	Partial: Requires cross-board automation & mapped columns	Yes: Convert an intake task; configured global field values transfer	Partial: Requires Control Center provisioning	No: Requests remain Jira work items	Partial: Intake creates a task; automation can create a project List
Custom values feed project & portfolio reporting	Yes: Configure columns, filters, grouping & totals	Partial: Board filters, grouping & cross-board dashboards	Partial: Global fields support universal reporting	Partial: Reports require matching columns across source sheets	Partial: Search and dashboards through JQL and gadgets	Partial: Fields can filter, group, calculate & feed dashboards
Custom data across the full project record set	Yes: Projects, tasks, issues, requests, users, companies & more	Partial: Columns on board items; boards model other record types	Partial: Fields on tasks, projects, portfolios & users	Partial: Columns on sheet rows; sheets model other record types	Partial: Fields apply to Jira work items & work types	Partial: Fields apply to tasks by location or custom task type
Custom record types that report like native work	Yes: Naming, numbering, assignment, files, client view & reports	Partial: Modeled with boards, items & templates	Partial: Custom task types; still tasks	Partial: Modeled with sheets, forms & rows	Partial: Custom work types; project-scoped	Partial: Custom task types; still tasks
Advanced structured input types	Yes: Table grids, signatures, dependent lists & system selectors	Partial: Rich columns plus WorkForms signatures; no table-grid field	Partial: Formula, ID & reference fields; no table-grid or signature field	Partial: Grid and conditional forms; no nested table or signature field	Partial: Cascading lists; tables and signatures require Marketplace apps	Partial: Formulas, relationships & files; no table-grid or signature field
Financial-data-aware field visibility	Yes: Custom field follows native project financial permissions	Partial: Generic column permissions on Pro & Enterprise	Partial: Generic private-field permissions	Partial: Controlled field exposure requires Dynamic View	No: No native role-based field restrictions	Partial: Generic field permissions on Business Plus & Enterprise