Custom Fields provide flexibility to capture additional data within the application. Specifically, custom fields can be added to requirements, test cases, test cases in your execution sets and incidents. This feature allows you to add additional fields according to your needs in order to record additional information against these entities. A wide selection of field types can be created including:

Text box

Single line free text field

Combo box

Single choice, multiple option drop down box

Multi Select

Multiple select, drop down box

Text Area

multiple line free text field

Check Box

Either/or option

Date

Free text date field

Radio Box Group

Single selection, multiple option

Check Box Group

Multiple selection, multiple option

Number

Free text number field

Time Span

Free text time span field ( e.g. 4d,2h)

Rich Text

Multiple line, free text field with formatting

Multi-Cascade Select*

Two level and multi-level drop down boxes

*When using the Multi-Cascade Select field for multi-level cascading select (>2 levels), picklists are not configurable within Enterprise Tester. Values will be pulled from a configured defect tracker e.g. JIRA. You must have a defect tracker configured in order to use this custom field.

Creating Custom Fields

To creating custom fields complete the following steps:

 

  1. Click on the ‘Admin’ tab.
  2. Click to expand ‘Extensions’ from your tree view.
  3. Click on ‘Custom Fields’.
  4. The Configure Custom Fields list view will display.

  5. Click on ‘Add’ from the window toolbar.
  6. The ‘Field Configuration’ screen will open.
  7. On the ‘Details’ tab, enter a name for your field.
  8. In the Label field, enter the name of the field as you would like it to appear on screen to users. For configuration details for the Multi Level Cascade Select field, please refer to Section 5.1.1.
  9. Click the drop down button on the ‘Type’ field to select the type of field you would like to create.
  10. If the field is mandatory to complete, click the ‘Required?’ field, otherwise leave it blank.
  11. Include a brief description in the Description field.
  12. Click on the ‘Entities’ tab to select the types of entities (Incident, Requirement, Script Run and Test Script) which will include the custom field. Note that you can use the same custom field across multiple entities.
  13. Click on the ‘Scope’ tab.  Here you can select the organization(s) and/or project(s) that will include the custom field.
  14. By adding scope for an organization, all projects for that organization will use the custom field for the entity selected.  You can add specific custom fields for specific projects by including them here. When you specify the scope, entities will be updated to include the new field i.e. requirements, scripts and incidents that have previously been created will be updated to include the new custom field.  If the field is mandatory, the user will be prompted to add this additional detail before saving.
  15. Click ‘Save Changes’ at the bottom right hand corner.
  16. The Configure Custom Fields list view will display.
  17. Click on ‘Add’ from the window toolbar.
  18. The ‘Field Configuration’ screen will open.
  19. On the ‘Details’ tab, enter a name for your field.
  20. In the Label field, enter the name of the field as you would like it to appear on screen to users.
  21. Click the dropdown button on the ‘Type’ field to select the type of field you would like to create.
  22. If the field is mandatory to complete, click the ‘Required?’ field, otherwise leave it blank.
  23. Include a brief description in the Description field.
  24. Click on the ‘Entities’ tab to select the types of entities (Incident, Requirement, Test Scripts) which will include the custom field. Note that you can use the same custom field across multiple entities.
  25. Click on the ‘Scope’ tab. Here you can select the organization(s) and/or project(s) that will include the custom field. Here you can also apply the custom field to all dependent projects or only to independent project. Apply the custom field to all dependent projects the custom field will be apply to all projects that are not marked as Independent n the project configuration screen. Please refer to the Managing Project help topic.
  26. By adding scope for an organization, all projects for that organization will use the custom field for the entity selected. You can add specific custom fields for specific projects by including them here. When you specify the scope, entities will be updated to include the new field i.e. requirements, scripts and incidents that have previously been created will be updated to include the new custom field. If the field is mandatory, the user will be prompted to add this additional detail before saving.
  27. Click ‘Save Changes’ at the bottom right hand corner.

Creating a Multi Cascade Select Custom Field

Creating a multi-cascade select custom field is similar to creating any other custom field with in Enterprise Tester.  The values used to populate the picklist values for the multi-cascade select field are pulled from the defect tracker e.g. JIRA. A defect tracker must be configured to create this custom field successfully. 

Enterprise Tester may need to perform a “Refresh Lookup” before new custom fields in your defect tracker are available within Enterprise Tester.  Please refer to the Refresh Lookups topic.

To create a multi-cascade select custom field:

  1. Follow the steps 1-8 described in Section 5.1.
  2. Click the drop down button on the ‘Type’ field and select “Multi Level Cascade Select”
  3. The “Options” section will display.  Select the defect tracker that contains the Multi Level Cascade Select Field. 
  4. Select the Multi Level Cascade Select field in the defect tracker to map to in the Field drop down.  The values stored for this field in your defect tracker will be used as the values in Enterprise Tester.
  5. If the field is mandatory to complete, click the ‘Required?’ field, otherwise leave it blank.
  6. Include a brief description in the Description field.
  7. Click on the ‘Entities’ tab to select the types of entities (Incident, Requirement, Test Scripts) which will include the custom field. Note that you can use the same custom field across multiple entities.
  8. Click on the ‘Scope’ tab.  Here you can select the organization(s) and/or project(s) that will include the custom field.
  9. By adding scope for an organization, all projects for that organization will use the custom field for the entity selected.  You can add specific custom fields for specific projects by including them here. When you specify the scope, entities will be updated to include the new field i.e. requirements, scripts and incidents that have previously been created will be updated to include the new custom field.  If the field is mandatory, the user will be prompted to add this additional detail before saving.
  10. Click ‘Save Changes’ at the bottom right hand corner.

When you view the screen you have applied your custom field to, it will display the field with the values from JIRA:

Configuring Pick Lists

When Combo Boxes, Multi Select boxes, Radio groups or Checkbox groups are created you will need to configure the selection lists.  These can be configured in the same way as other non – user defined drop down fields.  Please refer to the Managing Picklist Values article. 

Sorting Custom Fields

Custom Fields can be sorted by entity. This allows you to specify the order that the fields will appear on your requirement, test script or incident. From the Configure Custom Fields screen:

  1. Click on the ‘Sort Fields’ button on your toolbar


  2. The Order Custom Fields screen will open. Click on the drop down to select the entity type.



  3. You can rearrange the order of your fields by either selecting your field and using the drag and drop functionality or by highlighting your field and clicking on the ‘Move Up’ or ‘Move Down’ buttons.
  4. Click ‘Save Changes’ from the toolbar.
  • No labels