Data sources
Configure SeaLights, Git or SCM settings, and Jira or Azure DevOps source queries.
Connect User Story Coverage to the systems that supply report input. Configure the work item query, SeaLights source, and SCM extraction rules here.
How data sources are organized
Most setups combine three input types:
Work item source — choose the Jira or Azure DevOps query that defines the report scope.
SeaLights — connect to the coverage source and report-generation settings.
Git and SCM — extract ticket IDs from commits, branches, or pull requests.
Which section answers which question
Which tickets or work items should the report include? — use Work item source.
Which SeaLights account and report window should the report use? — use SeaLights.
How are ticket IDs extracted from source control activity? — use Git and SCM.
Work item source
User Story Coverage supports query-based work item selection from Jira and Azure DevOps.
Typical use cases
Report coverage for the current sprint
Report coverage for a specific epic or release
Publish coverage for work items changed in a date range
Query model
Use a query that returns the exact work items you want in the report.
Keep queries narrow. Start with a sprint, iteration, epic, or recent date range.
Test the query in Jira or Azure DevOps before you run report generation.
Use these settings when Jira or Azure DevOps supplies the work items for your report. Configure the source query here, then keep publishing target settings in Publication targets.
Use this when you are using Azure DevOps.
✅ Prerequisites
An Azure DevOps organization and project
A PAT-based authorization header value
A WIQL query that already works in Azure DevOps
🚀 Steps
📤 Expected Outcome
The query returns the exact work items for the report. Child work item expansion follows child_levels.
SeaLights
Use the sealights block for authentication and report generation behavior.
Git and SCM
Use the scm block to extract ticket IDs from commits and branches.
Regex examples
Jira keys —
"[A-Z]+-[0-9]+"GitHub issues —
"#[0-9]+"Azure DevOps IDs —
"[0-9]+"Custom multi-type pattern —
"\\[(FEAT|BUG|TASK)-[0-9]+\\]"— matches commit messages like[FEAT-123] Add user authenticationor[BUG-456] Fix login redirect issue
Validation tips
Confirm your regex matches real commit messages.
Keep
coverage_days_backlong enough for your release cycle.Test Jira queries and WIQL queries in the source system first.
Leave
verify_sslenabled unless troubleshooting requires otherwise.
Use Source Tagging for source-tagging command details and FAQ for common query questions.
Last updated
Was this helpful?

