Since version: 2.6.0
By default, the system loads a checklist template depending on work item /document type. You can define it via specifying the property
nextedy.checklist.YOUR_WI_TYPE.YOUR_CHECKLIST_ID.workItemTemplateId=EL-120
You can reconfigure such system behaviour and specify what built-in or custom field controls what template applied.
Example:
Imagine you have a work item custom field "requirementType", which is the enumeration that has two options "system" or "software".
You want a checklist "requirementReady" to be loaded from a template that is different for system or software requirements.
First, you set that the requirementType is a control field.
You may set it in a general view for all WI types as below:
nextedy.checklist.workitem.requirementReady.controlField=requirementType
or for the specific WI type only (in this case, WI type is 'requirement'):
nextedy.checklist.workitem.requirement.requirementReady.controlField=requirementType
and second, you can define the templates:
nextedy.checklist.system.requirementReady.workItemTemplateId=EL-120 nextedy.checklist.software.requirementReady.workItemTemplateId=EL-121
The same applies for Documents, just use the property:
nextedy.checklist.document.CHECKLIST_ID.controlField=DOCUMENT_CUSTOM_FIELD _ID
All configuration properties are stored in Project Administration > Configuration Properties.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article