Create 'project-specific' user fields for a requirement entity for a project linked to template
When you have created a project from a template, the user fields created for that requirement entity get passed along to the project. However, if you have a requirement user field that should only apply to one project, adding that user field to the template, applies that field to all projects linked to the template. We need to be able to add user fields for an entity specific to an individual project even if that project is linked to a template.
Re: Create 'project-specific' user fields for a requirement entity for a project linked to template
You can either add it as a new field only in the specific project, or you can add it to the template and push it out to all projects, and then hide it using the workflow in the projects where it is not relevant. Which approach you choose depends on if you expect the field to be needed in more than a single project.
[Please do not contact me off line for receiving support. Use the forum!]