I’d like to request an enhancement to custom fields: the ability to make a custom field linked/mapped so that it behaves as a single source of truth across a project.
What I’m asking for
When a value is entered/updated in a custom field in one place (ex: Project Info), that same value should automatically populate anywhere that same custom field appears elsewhere in the project (ex: tasks/subtasks used later in the workflow).
Why it’s needed
Today, teams often have to re-enter the same information multiple times (or copy/paste), which creates risk that reviewers/workers see a blank or outdated value. A linked field would:
- reduce duplicate data entry
- prevent inconsistencies
- improve handoffs during review/approval phases
- make templates/workflows more reliable
Example use case
In a project I’m working on, we have a project-level custom field called “Sponsor Link” on the Project Info page. Later during peer review, the reviewer needs that same sponsor link available on the review task(s).
I’d like the Sponsor Link field to already be populated on those tasks automatically (and stay updated if the link changes).
Ideal behavior (optional)
- Admin option when configuring the custom field like “Link to Project/Parent value” (or “Inherit from Project/Parent”)
- Option for child locations to be read-only/inherited or allow override with a clear indicator
- Updates propagate automatically to all linked instances
