Problem definition

Currently, when using the basic search, it's not possible to distinguish between custom fields that were created for next-gen projects and the ones for classic projects.

Impact

When trying to use the basic search, if the custom fields have the same name, it's not possible to identify which ones are from the next-gen project (and which project), and the ones from the classic projects. This adds a level of difficulty on performing searches for specific projects or even to evaluate what custom fields are in use.

Suggested resolution

Add the possibility to distinguish classic and next-gen custom fields. Example: using a tag on the name.