Qase Docs
Help CenterAPI DocsRoadmapSign up for free
  • General
    • Qase docs
    • Get started with the Qase platform
      • Account settings
      • Projects
      • Test suites
      • Test cases
        • Test Case Parameters
        • Test case review
        • Shared steps
        • Import test cases
        • Export test cases
        • Trash bin
        • Muted Tests
        • System fields
        • Nested steps
        • Test case actions
        • Filters
      • Requirements Traceability Report
      • AI Test Case Generator
    • Execute testing
      • Test plan
      • Test runs
      • Configurations
      • Environments
    • Issues tracking
      • Defects
      • Milestones
      • Requirements
    • Analytics
      • Dashboards
      • Queries (QQL, Qase Query Language)
      • Saved queries
    • Webhooks
      • Test Case
      • Test suite
      • Test plan
      • Shared step
      • Milestone
      • Custom field
      • Test run
      • Defect
      • Test review
  • AIDEN
    • AIDEN - QA Architect
  • Guide: Action editor
  • Administration
    • Workspace management
      • Users
      • Invites
      • Groups
      • Roles
      • Fields
      • Custom fields
      • Notifications
      • Tags
      • Attachments
      • Audit logs
      • Hotkeys
    • SSO / SAML instructions
      • AzureAD
      • OneLogin
      • Google Workspace
      • Okta
      • JumpCloud
    • SCIM
      • User lifecycle management with SCIM
      • Enable SCIM
      • Users
      • Discovery features
      • Errors
    • Security
      • SOC 2 Type II / SOC 3
      • ISO/IEC 27001:2022
      • Penetration testing report
      • Subprocessors
      • Qase IP addresses
    • Billing
      • Billing options
    • Subscriptions
      • Free plan
      • Startup plan
      • Business plan
      • Enterprise plan
  • Apps
    • Issue tracking
      • Jira Cloud
      • Jira Server/Datacenter Plugin installation
      • GitHub
      • Asana
      • Linear
      • Monday
      • ClickUp
      • Trello
      • Azure DevOps
      • GitLab
      • YouTrack
      • Redmine
    • CI/CD
      • Jenkins
      • BitBucket
      • GitHub CI
      • GitLab CI
    • Chats
      • Slack
  • Automation
    • Qase API
    • Reporters
      • JavaScript
        • Playwright
        • Cypress
        • Mocha
        • Newman
        • Jest
        • WebDriverIO
        • CucumberJS
        • TestCafe
      • Python
        • Pytest
        • Robot Framework
        • Behave
        • Tavern
      • Java
        • TestNG
        • JUnit 4
        • JUnit 5
        • Cucumber 3 (jvm)
        • Cucumber 4 (jvm)
        • Cucumber 5 (jvm)
        • Cucumber 6 (jvm)
        • Cucumber 7 (jvm)
      • PHP
        • PHPUnit
        • Codeception
      • Kotlin
        • Kaspresso
    • Qase CLI App
      • XCTest
Powered by GitBook
On this page
  • What are custom fields in Qase?
  • Create custom fields
  • Sort the Custom Fields
  1. Administration
  2. Workspace management

Custom fields

PreviousFieldsNextNotifications

Last updated 2 months ago

Custom Fields are available in , , and subscriptions

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 , , or .

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.

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:

Creating Values:

  1. Click and hold the 6 dots to drag and drop your values when organizing their order.

  2. Click the default "plus" icon to open the icon customization options.

  3. You can choose from the default colors or input the Hex color code for the icon.

  4. You can enter the icon code starting with "fas fa-" followed by the icon name chosen from the provided external link.

  5. Add a new value input field

  6. Delete a value input field

When exporting into CSV, your Custom Fields will appear as new columns on the far right of your CSV file.​They will be named "cf_1", "cf_2", "cf_3"... following the order of creation of your custom field in your Workspace Fields settings.


Sort the Custom Fields

By default, custom fields are arranged in chronological order based on their creation time, meaning the most recently created field appears at the bottom of the list.

However, if you want certain fields to be displayed at the top for easier access, you can adjust their order.

To do this, go to Workspace > Fields, select any custom field, and update its order value to change its position.

You can also sort the list by the order field to view the updated arrangement.

Startup
Business
Enterprise
Test Cases
Test Runs
Defects