Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
Absent Member.. CodyG Absent Member..
Absent Member..
413 views

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.

0 Likes
1 Reply
Knowledge Partner Knowledge Partner
Knowledge Partner

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.

Jan Czajkowski

[Please do not contact me off line for receiving support. Use the forum!]
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.