Skip to content

Latest commit

 

History

History
63 lines (40 loc) · 8.34 KB

custom-fields.md

File metadata and controls

63 lines (40 loc) · 8.34 KB
Raw

Custom fields

What are custom fields in Qase?

Obviously, test scenarios come with all varieties of data connected to them. It is pretty much impossible for us at Qase to predict every single data point you want to record for your Test Cases, Test Runs, or Defects. So instead of trying to cover all bases or giving a bare minimum, we provide you with Custom Fields - a tool to create your own custom data entry points.

⚠️Custom Fields are available in Startup, Business, and Enterprise subscriptions

{% embed url="https://youtu.be/SnXr_WPJiMc" %}

{% embed url="https://www.youtube.com/watch?v=o7YiwJpRmkA" %}

You'll need to create these Custom Fields first to be able to fill them in. To get started, navigate to the Workspace settings' "Fields" section:

Create custom fields

Create a new Custom Field by clicking "+ Create New Custom Field", configure your Custom Field, and define what it will be representing:

  • Title: give a brief descriptive name to your Custom Field (Title is the only mandatory parameter).

  • Entity: define which Qase entities your Custom Field will apply to - Test Cases, Test Runs, or Defects. This parameter is a single-choice one, so you cannot select "Test Cases" AND "Test Runs"; if you need to track similar data for both Runs and Cases, you'll need to create two separate Custom Fields for that.

  • Type: select from a dropdown which data type will be used in this Custom Field. Depending on the type of data selected, the options below will be different.
    ​NB: once a custom field has been created, its type cannot be changed.

  • Enable for all projects: choose which Projects your custom field should be applied to. If you have to capture the same data uniformly in multiple projects, you don't have to create duplicates of a field for each project - create a custom field once and apply it to various projects:

  • Placeholder: provide a sample value that will be appearing in a field in a faded color, while the Custom Field remains empty. This can help avoid confusion about what should go into the field.

  • Default value: to avoid having Custom Fields left blank, you can automatically insert a default value.

  • Required field checkbox: checking this box will make a field mandatory; an entity with such Custom Field will not be created until Custom Field is filled in.

  • Values: Available for Multiselect and Selectbox types of data, this area allows you to define values to choose from when filling out a custom field:


  1. Rearrange your values by long pressing this button and moving the field from top to bottom.
  2. Customize each value with icons of your choice.
  3. Add a new value input field
  4. Delete a value input field

\