Custom Fields are not showing in subtasks, showing as "inherited fields"

English Forum Ask the Community
,
1

We upgraded from Advanced to Enterprise today and immediately noticed an issue with existing custom fields on subtasks across our current projects/templates.

Issue

In existing projects, when editing any legacy custom field on a subtask:

  1. We select a value.

  2. The value appears briefly.

  3. It then disappears.

  4. The field shows under Inherited Fields.

This is happening across multiple projects and affects approximately 12 existing custom fields.

What We Tested

Existing Project + New Custom Field

We created a brand new single-select field inside the same affected project.

Result: Works normally on subtasks.

Brand New Blank Project

Created a new blank project and tested custom fields.

Result: Works normally.

Likely Cause

This appears isolated to pre-existing legacy custom fields after the Enterprise upgrade, rather than a browser, permission, or project issue.

Requested Help

Please review whether the upgrade changed field mappings, permissions, or legacy custom field behavior.

Specifically:

  1. Can these existing custom fields be repaired?

  2. Is there an admin setting causing subtasks to use inherited fields only?

  3. Is this a known migration issue from Advanced to Enterprise?

This is impacting our template rollout and active workflows.

2

Welcome, @Joshua_M,

I tried to reproduce this (without upgrading) and couldn’t.

Try these troubleshooting steps, then please create a support ticket: see How to contact our Support Team.

Thanks,

Larry