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 the fields for?
  • Accessing Field settings
  • System fields
  • Custom fields
  1. Administration
  2. Workspace management

Fields

PreviousRolesNextCustom fields

Last updated 4 months ago

What are the fields for?

The Fields section of the Workspace allows the user to manage system fields and custom fields pertaining to the workspace.

In the fields section, you can create, edit or view all system and custom fields that exist in the workspace.

Accessing Field settings

There are multiple options available to you to access the field section.

  1. Click on “Fields” in the workspace page

  1. Click on “Configure fields” when creating or editing a test case.

System fields

Priority

choose your test cases' priority. Eg- Low, Medium, High, or Not Set

Severity

options for your test cases' severity. Eg- critical, blocker, normal etc

Type

select the types of testing that are applicable for your test case

Behavior

can be either Destructive, Negative, Positive, or Not Set

Description;

Pre & Post conditions

to provide additional details for more context about a test case

Status

can be either Active, Draft, or Deprecated

Layer

options to pick a layer for the test case, whether it's an end-to-end, API, or a unit test

Is Flaky

if a test case is unstable, you can mark it as flaky

Automation Status

you can choose from Automated, or Manual

To be automated

a checkbox property only available for those cases that have Automation status set to Manual.

Result Status

a test runs field, for all possible result statuses that can be added to a test case.

Custom fields

It is difficult to predict the unique parameters or properties your Test Case, Test Run, or Defects might require. Custom Fields can help.

Create your own Custom Fields of various data types to store any additional information about your test cases, test runs, or defects not covered by default properties.

If you haven't created any Custom Fields yet, you won't see this section in the Test Case, Test Run, or Defects configuration.

A system field can be, optionally, switched OFF via the section.

There is also the possibility to modify the values of system fields (available on the , , and plans):

Custom Fields are available in , , and subscriptions

fields
Startup
Business
Enterprise
Startup
Business
Enterprise