Version Package lets you group any set of work items into a structured versioned package — keep items live and synced with Azure DevOps or pin them to a specific revision, compare versions, manage variants for different regions or platforms and generate audit-ready reports all without leaving ADO
ADO backlogs are not packages. Sprints do not capture revisions. Release scope disappears the moment work items change.
When a release goes out your team has no formal record of exactly which work items were included and at which revision. Reconstructing the requirement set for a post-release audit means manually searching revision histories across the entire backlog.
Sprints organize work by time, not by requirement hierarchy. There is no ADO-native way to group a specific set of work items into a structured, template-driven package that enforces the correct Epic-Feature-Story-Test hierarchy across every delivery.
Teams managing product variants for different regions, platforms or regulatory requirements maintain separate copies of requirement documents with no traceability between them. When the core requirement changes every copy must be updated manually — and none of them stay in sync.
No spreadsheets, no Word exports, no manual grouping. Version Package structures, versions and tracks your requirement sets inside Azure DevOps.
Open the Template Designer and define your work item hierarchy — Epic at the root, then Features, User Stories, Test Cases and Tasks. Set default field values, display properties and numbering per node. Mark nodes as Recursive if nesting is needed. Save once and reuse across every package.
Select your template, name the package and source work items by query or search. ADO automatically pulls the full linked hierarchy beneath your selected Epics. Every work item is Live by default — always synced with Azure DevOps. Pin any item to a specific revision when needed.
Create named version snapshots at any milestone. Compare any two versions side by side with a color-coded diff. Send the package for formal review, generate a Smart Report in Word or PDF, or save directly to Document Management — all from the same toolbar.
Design your work item hierarchy once in the Template Designer — set Root Work Item Type, default field values, inherited properties and display columns per node. Save to the Meta Templates library. Select any saved template when creating a new package and the full hierarchy is applied instantly.
Create a package variant as an exact copy of the current package in a target project. Modify specific work items in the variant to meet regional or platform-specific requirements while maintaining traceability back to the source. Enable propagation rules to automatically push source changes to all variants.
Create named version snapshots at any milestone with a label and comment. Use Compare to Version to see a color-coded diff between any two versions of the same package. Use Compare with Package Variant to compare the current package against any of its source or target variants — green for added, red for deleted, yellow for updated.
Nest packages inside each other as Sub Packages, or connect them with directional Linked Packages — Up for upstream and Down for downstream. Create associated packages from scratch or link existing ones. Right-click any work item to scope a new sub or linked package to that specific item.
Use Copilot4DevOps inside any package to draft new work items and insert them into the VPM. Transform content by summarizing, paraphrasing, translating or converting to Gherkin, Use Case or User Story format — applied directly to work item fields without leaving the package.
Open the Insert Work Items pane and source items by query or search. Insert a single item, a multi-item selection or an entire parent-child hierarchy in one drag. A green highlight confirms a valid drop position. Every inserted item connects to ADO in real time and refreshes on Run.
Open the Links side pane for any selected work item to see all its ADO relationships grouped by type — Child, Parent and Related. Work items already included in the current package are highlighted so you can immediately see what is covered. Add new links between any work items directly from the pane without leaving the package.
Click Save As to export any package as a formatted Word document or PDF using your organization's branded dotx templates. Save directly to the Document Management library for team-wide access without downloading. Choose from saved templates or upload a custom template for fully branded output.
Revision pinning, package locking, version history, variant traceability and formal review integration — all native to Azure DevOps.
Click Review in the toolbar to send the package for structured review without leaving Version Package. Add Reviewers and Approvers, configure rules and send. All participants receive email notifications. The review appears in Review Management and generates an Approval Audit Report on closure.
Click Lock Package to disable all edit actions on the package immediately. A locked package cannot be modified by any team member until an authorized user explicitly clicks Unlock Package. Use this to protect formally reviewed and approved packages from unintended post-approval changes.
Generate a formatted Smart Report from any package using your organization's branded templates and stylesheets. Export as Word, PDF or HTML, or save directly to the Document Management library. The report captures the full package hierarchy, work item content and field values in one formatted document.
The Variants tab shows the Source — which package this variant was derived from — and all Target variants created from this package. Navigate directly to any source or target variant by clicking its name. Every variant relationship is two-way and permanently recorded.
Each work item in a package can be Live or pinned to a specific revision independently. Set Version lets you choose from all available ADO revisions with a Version ID and date. Your package reflects precisely what you need — not just the latest state.
Every version created is logged with a label, version number, creation date, creator and status. Open any historical version in read-only mode to reconstruct the exact package state at any past milestone. The complete version list is always available in the Version Management dialog.
From product owners packaging sprint scope to compliance managers creating locked audit packages — every role has a specific workflow inside Version Package.
Group a formal requirement set into a Version Package using the requirements query. Use the Insert Work Items pane to add individual items or full parent-child trees. Use Copilot4DevOps to generate User Stories from Features directly inside the package. Create a named version when the requirement set is agreed and send for review from the toolbar.
Create a Version Package for each system architecture layer — System, Subsystem, Software, Hardware — using a custom template with the correct hierarchy. Pin specific work items to the revision approved at each design review. Compare the PDR version to the CDR version and generate a color-coded difference report as formal scope change evidence.
At each release gate create a named version snapshot of the release requirement package with a label matching the release version — for example v4.2-rc1. Lock the package after formal sign-off to prevent post-approval changes. Generate a Smart Report of the locked version as the formal release baseline document for the delivery team and stakeholders.
Create Version Packages for each compliance control domain. Pin work items to the revision that was formally reviewed. Lock the package after the review cycle closes. Generate a Smart Report as the formal compliance documentation for the audit package. Use the version history as the tamper-evident record of when each package state was captured.
Create a test package grouping test requirements, test cases and linked user stories using the Tested By link type. Use Set Version to pin test cases to their review-approved revision before each test cycle. After testing compare the pre-test version to the current state to identify any test requirements that changed during execution.
Create a safety requirement package with a custom template structured as Safety Goal → FSR → TSR. Create package variants for different ASIL levels — the variant starts as an exact copy of the source and is modified for the target safety integrity level. Enable propagation rules so that changes to shared source safety requirements flow into all variants automatically.
Manage formal configuration items as Version Packages — SRS package, ICD package, STP package. At each configuration baseline event create a named version snapshot with a label matching the milestone — PDR, CDR, TRR. Lock each package immediately after formal review. Use the version history as the immutable configuration baseline record.
Create a Version Package of design input requirements and verification records for each regulatory submission. Pin all work items to the revision approved at the design review. Lock the package before submission. Generate a Smart Report as the formatted submission document. If the FDA or Notified Body requests changes unlock, update and create a new named version before re-submitting.
Create a Version Package for each sprint using the ADO query as the source. ADO automatically pulls the full Epic-Feature-Story hierarchy beneath selected Epics. Create a named version snapshot before sprint planning. After the sprint compare the current state to the pre-sprint version to see what changed during execution.
Create a top-level program requirement package and use Linked Packages — Down direction — to connect it to each delivery team's project package. When a program-level requirement changes use propagation rules or manually update the linked downstream packages. Navigate between program and delivery packages directly from the Associated Packages pane.
Create Version Packages for URS, Functional Specification and Test Protocol work items at each CSV phase. Pin each package to the phase-acceptance revision and lock it after IQ, OQ and PQ sign-off. Generate Smart Reports from each locked version as the formal phase documentation included in the GAMP 5 validation lifecycle evidence package.
Use Associated Packages to link the prime contractor's program requirement package to the supplier's ADO project package using a Down directional Linked Package. When the prime requirement changes the linked relationship is visible in both projects. Generate a Smart Report from the linked package and save to Document Management for the supplier to access.
Each use case below covers a real compliance scenario, the specific VPM capability that solves it and the exact workflow inside Azure DevOps.
Create a master safety assessment Version Package and add separate Sub Packages for each system function — one for FHA, one for PSSA and one for SSA. Each sub-package is scoped to its own work item set. Navigate between assessment levels directly from the Associated Packages pane without losing context of the master package.
Create a base IEC 60601-1 safety requirements package for the device platform and use Down Linked Packages to connect it to each product variant's project. When a platform-level safety requirement changes the linked relationship is visible in all downstream product packages — giving the product family a live traceability chain without maintaining separate documents.
Create a base AUTOSAR software requirements package and create variants for each ECU configuration — gateway, powertrain and ADAS. Enable propagation rules so changes to shared platform requirements flow into all ECU variants automatically. Use Compare with Package Variant to identify configuration-specific deviations between the base and any ECU variant.
Create named version snapshots of the railway change risk assessment package at each CSM phase — Hazard Identification, Risk Acceptance and Independent Assessment. Lock each version after the Independent Safety Assessor sign-off. Compare CSM phase versions side by side to show the ERA exactly what changed in the risk assessment between phases.
Create a standardized ICH Q10 package template with process performance monitoring, CAPA and change management nodes as the mandatory hierarchy. Every site quality team creates their quality system packages from this template — enforcing the ICH Q10 structure across all manufacturing sites without relying on individuals to remember the correct work item hierarchy.
Create a Version Package of PCI DSS control implementation requirements at the start of each quarter. At the end of the quarter compare the current version to the start-of-quarter version using the color-coded Compare tab. Green items show new controls added, yellow shows updated implementations — giving the QSA an instant view of what changed in the cardholder data environment.
Create a master FISMA authorization package and add Sub Packages for each system boundary component — cloud infrastructure, on-premises servers and third-party integrations. Each sub-package contains the NIST controls applicable to that component. The master package gives the Authorizing Official a complete authorization picture while each component team manages only their own sub-package independently.
Create a Version Package for the MIL-STD-498 Software Requirements Specification work items. Select Feature-level work items and use Copilot4DevOps Transform to convert high-level capability descriptions into structured software requirement statements. Apply the Summarize transformation to condense lengthy inherited system requirements into concise software-level requirement titles — all without leaving the package.
Create a reusable FHIR integration requirements package template with Capability Statement, SearchParameter and OperationDefinition nodes as the mandatory hierarchy. Each integration project team creates their package from this template — ensuring every FHIR integration project captures the same compliance-required requirement categories without any manual restructuring or starting from a blank package.
Select the full asset management requirement hierarchy from the ADO backlog — Asset Policy epics down through Strategic Plans, Objectives and Control Plans — and insert the complete parent-child tree into the Version Package in a single drag. The hierarchy lands with the correct structure intact. Run to refresh all items against the latest ADO state at any time.
Create a Version Package for each CMMI process area — Requirements Management, Project Planning, Verification. Create a named version snapshot at each CMMI appraisal cycle. Compare the current appraisal version to the previous one and generate a color-coded difference report showing the Lead Appraiser exactly which practice implementations changed between appraisal cycles.
Create a Version Package of ETSI EN 301 489 EMC conformance requirements. When the standard is revised create a new named version snapshot reflecting the updated requirement set. Compare the previous standard version to the updated version using the color-coded Compare tab — immediately identifying which EMC requirements changed, were added or were removed in the new standard revision.
Named version snapshots with label, creator and timestamp are permanently recorded. Lock a package after sign-off to prevent post-approval changes. Generate a Smart Report from any version in one click. Compliance teams get audit evidence that shows exactly what was in scope at any milestone — without manual reconstruction.
Regulated teams managing product variants for different markets create package variants instead of maintaining separate documents. Each variant traces back to its source. Propagation rules push source changes to all variants automatically. Traceability between the base and every variant is visible in the Variants tab at all times.
Every work item in a package defaults to Live — always synced with Azure DevOps. Click Run to refresh the package against the latest data. Insert a full Epic-Feature-Story-Test hierarchy in a single drag. Teams build accurate, structured release packages from the backlog without manual copying or re-entry.
Instead of asking teams what is in scope for the next release leadership opens the Version Package and sees the complete structured requirement set directly from Azure DevOps — organized, versioned and always reflecting the latest agreed scope.
Version Package is part of MR NextGen — built natively inside Azure DevOps. Group any set of work items into a structured versioned package, create named snapshots at every milestone, manage variants for every platform and generate audit-ready reports all in one place.
Version Package connects to every other MR NextGen module — launch reviews, create baselines and save reports all without leaving your package.
Create living requirements documents by inserting work items from your ADO backlog. Save Smart Doc outputs directly to Document Management. Launch a baseline or review from any Smart Doc without navigating to a separate module.
Explore Smart Docs →Build intersection and horizontal traceability matrices from live ADO work items. Use a saved query as the source — the same query that drives your Version Package — to visualize coverage across the package work item set.
Explore Traceability →Freeze any requirement set as an immutable snapshot at any milestone. Create a baseline directly from a completed Review or from the ADO Backlog without opening the Baseline module separately.
Explore Baseline →Collect formal approvals on any requirement set inside Azure DevOps. Click the Review button from inside any Version Package to launch a fully pre-loaded review request without navigating away.
Explore Review Management →Save Smart Reports from Version Package directly to the Document Management library in one click. Every report is versioned, organized and accessible to the whole team without manual downloading.
Explore Document Management →The only AI requirements assistant built natively inside Azure DevOps. Use Elicit to generate User Stories and Test Cases inside your package, and Transform to summarize, paraphrase or convert content — without leaving Version Package.
Explore Copilot4DevOps →
End-to-end requirements management in Azure DevOps.
AI-powered assistance for DevOps workflows.
Autonomous AI agents for DevOps execution.
Real-time data sync across tools and systems.
