Skip to main content

Task tracking connection

Open with Workspace → Connections → Task Tracking… on the main menu bar. A modal dialog for connecting to Jira or Azure DevOps. Rally is no longer supported.

The Task Tracking dropdown at the top picks the provider; the form below changes accordingly.

Bottom buttons

ButtonWhat it does
ConnectActivate the selected connection (default action).
TestVerify the connection works without making it active.
CancelClose the dialog without changes.

Jira

FieldWhat it holds
Server URLYour Jira instance URL, e.g. https://your-company.atlassian.net.
AuthenticationDropdown: picks the auth method. For Jira Cloud, use Api Key Authentication.
UsernameYour Atlassian account email address (e.g. user@company.com).
PasswordShown when password-based auth is selected. Masked.
API KeyShown when API-key auth is selected. Paste your Jira API token here. Masked.
Web ProxyOptional proxy URL if Jira is reached through a corporate proxy.
Proxy UsernameUsername for the proxy (if it requires auth).
Proxy PasswordProxy password. Masked.

Getting a Jira API token

Jira Cloud requires an API token instead of a password. To create one:

  1. Log in to id.atlassian.com/manage-profile/security/api-tokens.
  2. Click Create API token, give it a label (e.g. "DataStar"), and click Create.
  3. Copy the token — it's only shown once.
  4. In DataStar, set Authentication to Api Key Authentication, enter your Atlassian email as the Username, and paste the token into API Key.

Azure DevOps

FieldWhat it holds
Server URLYour Azure DevOps organisation URL, e.g. https://dev.azure.com/your-org. For on-premises Azure DevOps Server, use the server URL instead.
AuthenticationDropdown: picks the auth method. Options include Managed Identity, Personal Access Token, and others depending on your environment.
Collection NameProject collection name. Defaults to DefaultCollection. On Azure DevOps Services (cloud) this is usually your organisation name.
Project NameThe Azure DevOps project that contains your work items. Leave empty to auto-detect from the workspace.
Tenant IdAzure AD (Entra ID) tenant ID. Required for OAuth-based authentication flows.
Client IdAzure AD application (client) ID. Required for OAuth-based authentication flows.
TokenPersonal access token (PAT). Required when using PAT authentication. Masked with a reveal button. Create one from Azure DevOps → User Settings → Personal Access Tokens.
Also use these settings for Version Control (TFVC)Checkbox: when ticked, the same server URL and credentials are reused for the workspace's TFVC version-control connection, avoiding duplicate configuration.