Skip to content

Configuration Checklist

This page summarizes everything analytiQa needs from you to configure your environment, grouped by area. Use it as a checklist when preparing for onboarding or a change. You don't need to write this file yourself, but it shows exactly what to gather. You'll enter it through a secure credential intake link, never by plain email or chat.


Example

# analytiQa configuration checklist — example values shown, replace with your own

core:
  instance_hostname: cx001.analytiqa.cloud   # Assigned by analytiQa
  azure_sso:                                  # Optional — only if you want Azure AD / Entra ID single sign-on
    enabled: false
    tenant_openid_config_url: ""
    client_id: ""
    client_secret: ""

jira:
  enabled: true
  url: https://your-company.atlassian.net
  username: you@your-company.com
  api_token: ""                                # Jira API token — see Getting Started
  filters:                                      # One or more — each is a JQL query or a saved Jira filter
    - name: "Platform"                          # Shown in dashboards; use the team / board / workstream name
      jql: 'project = PLAT'
    - name: "Falcon"
      jql: 'project = WEB AND "Squad" = Falcon'
    - name: "Mobile"
      saved_filter: "Mobile squad - qTest sync" # Must be shared with the analytiQa Jira account
  history_from: "2026-01-01"                    # How far back the first extraction goes
  custom_fields: [Team, Sprint, Fix Version]    # The defaults; add any others (e.g. Story Points)
  polling_interval_minutes: 15                  # How often we check for new/updated issues

qtest:
  enabled: true
  base_url: https://your-instance.qtestnet.com/
  access_token: ""
  project_name_match:
    - ".*"                                      # Regex — which projects to include
  modified_after_days: 7                        # Historical look-back window
  polling_interval_minutes: 60

tosca:                                          # Set up on your own Windows machine, not through the secure link
  enabled: true
  extractor_machine: "Windows machine with Tosca Commander installed"
  workspace_path: "C:\\Tosca_Projects\\Tosca_Workspaces\\MyProject\\MyProject.tws"
  login_mode: tosca-server-client                # tosca-server-client (recommended) | tosca-server-pat | direct-db
  # Your Tosca Client Secret, token or password stays on your machine, in the extractor's appsettings.json
  data_out_path: "D:\\analytiqa\\export-assets" # Default export folder; change if the machine has no D: drive
  search_last_n_hours: 72                        # Historical look-back window for each run
  schedule: "agreed during onboarding"

tosca_cloud:
  enabled: true
  tenant_url: https://yourcompany.my.tricentis.com
  token_url: ""                                 # From <tenant>/_identity/apiDocs/swagger -> Authorize
  client_id: ""                                 # Tricentis_Cloud_API application (administrators only)
  client_secret: ""
  portal_username: ""                           # Optional: a Tosca Cloud user without MFA, only if we ask for it
  portal_password: ""
  workspaces: all                               # Or a list of workspaces
  history_from: "2025-10-01"                    # How far back the first extraction goes
  polling_interval_minutes: 15

oss_dashboards:
  admin_login: "provisioned by analytiQa"        # Your dashboard admin credentials are issued to you, not supplied by you
  sso: "see core.azure_sso above, if desired"

Field Notes

Core

Field Required Notes
Instance hostname Yes Your dashboard/docs URL — assigned by analytiQa
Azure SSO No Only needed if you want to log in to dashboards with your organization's Microsoft/Entra ID account

Jira

Field Required Notes
URL, username, API token Yes The Jira account analytiQa uses. It must be able to browse every project in your filters
Filters Yes One or more, each with a name plus either jql or saved_filter. Don't exclude Done issues
History from No How far back the first extraction goes. Ongoing runs pick up recent changes only
Custom fields No Team, Sprint and Fix Version by default. Fields that don't exist in your Jira are skipped

See Jira Extractor Setup for how to obtain each value, plus filter examples.

qTest

See qTest Extractor Setup for how to obtain each value.

Tosca

Field Required Notes
Extractor machine Yes A Windows machine with Tosca Commander installed. You install the extractor and the Fluentd log shipper on it
Workspace path Yes Full path to the .tws file on that machine. The workspace must be closed whenever the extractor runs
Login mode Yes Tosca Server Client ID + Secret (recommended), Tosca Server Personal Access Token, or repository username + password. The Tosca Server modes need a workspace created with the Tosca Server connection type. Each mode has its own example settings file in the extractor package
Export folder No Defaults to D:\analytiqa\export-assets. If the machine has no D: drive, choose another folder and use it in the Fluentd configuration too
Search window No How far back each run looks. Runs are incremental, so a run that finds nothing new is normal

Tosca isn't part of the secure credential intake link. Your Tosca login is entered into the extractor's settings on your own machine, usually in a session with your technical contact. See Tosca Extractor Setup for the full steps.

Tosca Cloud

Field Required Notes
Tenant URL Yes The address you use to open Tosca Cloud, https://<tenant>.my.tricentis.com
Token URL Yes Open https://<tenant>/_identity/apiDocs/swagger, click Authorize and copy the Token URL
Client ID, client secret Yes Of the Tricentis_Cloud_API application. Only a Tosca Cloud administrator can read them
Portal account No A Tosca Cloud user without MFA. Only needed if your tenant rejects the client ID and secret for plan and usage data
Workspaces No All workspaces by default
History from No How far back the first extraction goes. Ongoing runs pick up recent changes only

See Tosca Cloud Extractor Setup for how to obtain each value.

OpenSearch Dashboards (oss)

You don't provide anything here — analytiQa provisions your dashboard login and shares it with you once your environment is ready.


Sending Us This Information

Contact your Qualtiva technical contact, or support@qualtiva.solutions if you don't know who that is. Say what you'd like to set up or change, and they'll send you a short-lived secure credential intake link, usually with a session to go through it together. Enter tokens and passwords only through that link.

Non-secret details, such as your list of Jira filters or qTest projects, can go in your request email or be discussed in the session. See Providing Configuration & Credentials Securely for the full process.