All articles

Fix Missing Custom Field in Item View

Overview

Custom fields can be viewed and interacted with from different views inside Wrike workspace. If you are having trouble finding the custom field in the Item view, checking the Custom Item Type (CIT) settings and the field's configuration can help.

Situation

A custom field is visible as a column in Table or Gantt view, but it does not appear in Item view.

To understand why this is happening, check if you're able to edit custom field values in Table or Gantt view. Depending on the result of your check, we suggest following a different troubleshooting flow.

Editing custom field values works

If you can edit the custom field values from the Table/Gantt Chart, check whether the affected item is a CIT or a regular task, project, or folder. If only a specific CIT is affected, the custom field you are looking for may be marked as Hidden in the CIT settings. To resolve this, contact your account admin or space admin and ask them to set the field to visible by clicking the eye icon in the CIT builder.

Editing custom field vales does not work

If you can't edit the custom field values from the Table/Gantt Chart, check if you can edit this custom field on other types of work items (task-based, folder-based, project-based) in the same location. Custom fields can be configured to use with specific item types only. It is not possible to populate certain item types with a custom field that has these item types disabled in its settings.

To check custom field settings from the Table view:

  1. Switch to the Table view.
  2. Find the custom field column and click on the three‑dot menu in the header.
  3. Click on Change field settings.
  4. In Applies to dropdown select the required item types.

Contact Support

If the steps described in this article didn't help solve the issue, please contact our Support team for assistance.

When sending a support request, please include the following information:

  • Troubleshooting steps you took.
  • Screenshot or video recording illustrating the issue.
  • Permalink to the affected folder/project/space.
  • Emails of user(s) experiencing the trouble.
Top

Related articles