Trajektori

Make delivery progress visible in Azure DevOps

Trajektori brings release planning, portfolio insights, and roadmap views into the Azure DevOps experience your teams already use.

It helps product owners, delivery managers, project leads, and teams answer practical questions quickly:

• What is planned for a release, and what is still missing?
• How are work items distributed across teams, states, priorities, or other fields?
• Which work is planned on the timeline, and where are the gaps or risks?
• Can different projects use the same way of working without forcing everyone into one rigid template?

Trajektori is designed for organizations that want a clearer portfolio view while keeping Azure DevOps as the source of truth for work items, permissions, and project context.

Three connected capabilities

Releases

Manage version-based releases as native Azure DevOps work items and connect delivery work to them. Each release acts as a clear delivery target, similar to a Fix Version: assign work items to a version, review everything planned for that version, and compare the release scope with the current state of the linked work.

• Browse releases in a dedicated Releases hub.
• View the release scope and all linked work items in one place.
• Link or unlink a release directly from a work item form.
• Select multiple backlog items and add them to a release in bulk.
• See release-linked work items in a dedicated work item tab.
• Open the linked items in the Azure DevOps query experience.
• Configure the columns shown in release overviews and release details per project.

This gives teams a practical version comparison: what was assigned to a release, what is currently in scope, and which linked items still need attention based on their Azure DevOps state. Releases use the Azure DevOps work item model, so teams can continue to work with familiar fields, states, permissions, and work item navigation.

Insights

Build configurable matrix and board views from the work item data already in Azure DevOps.

• Choose the fields used for the X and Y axes.
• Group date fields by week, month, quarter, or year.
• Combine projects in one view with project-specific filters and date sources.
• Create filter groups with AND logic within a group and OR logic between groups.
• Use standard fields, tags, Parent, and automatically mapped date fields.
• Configure the order and visibility of axis values.
• Search by title or work item ID.
• Filter by period and assigned person.
• Open work items directly from the board.
• Move items to another date or field value with a confirmation step.
• Share public Insights through a link while keeping private Insights restricted.

Insights are useful for portfolio reviews, cross-team planning, delivery tracking, dependency discussions, and operational reporting without maintaining a separate reporting dataset.

Roadmaps

Turn work item data into a configurable timeline for planning and communication.

• Combine one or more projects in a roadmap.
• Filter each project independently.
• Use explicit work item date fields or derive dates from Iteration Path and sprint dates.
• Choose a timeline scale of week, month, quarter, or year.
• Group work into swimlanes using a work item field or Parent.
• Configure the order and visibility of swimlane values.
• Search and filter by period or assigned person.
• Distinguish planned items from items without valid dates.
• Update dates or iteration assignments through a confirmation flow.
• Open work items directly from the roadmap.
• Share public roadmaps through a link while protecting private roadmaps.

Roadmaps give stakeholders a shared view of delivery timing while teams retain ownership of the underlying Azure DevOps work items.

Flexible by design

Every Azure DevOps organization has its own process. Trajektori is built to adapt to that reality.

• Select the projects, fields, date sources, filters, columns, and grouping values that fit your process.
• Use sensible defaults so a basic view can be created without extensive setup.
• Add multiple projects with different filters and date configurations.
• Keep manual ordering and visibility settings when new work item values appear.
• Support both explicit date fields and sprint-based planning.
• Preserve existing configurations when models evolve through normalization and safe defaults.
• Hide options that do not apply in the current context.

Flexibility should reduce work, not create another administration project. Trajektori keeps advanced configuration available while presenting familiar Azure DevOps controls for everyday use.

Native to Azure DevOps

Trajektori is intended to feel like part of Azure DevOps rather than a separate reporting product.

• Uses Azure DevOps work items and project context.
• Uses the Azure DevOps Extension SDK and Extension API.
• Uses official Work Item Tracking REST APIs and WIQL for work item data.
• Uses Azure DevOps UI components and interaction patterns such as pages, cards, tables, dropdowns, command bars, dialogs, and master-detail layouts.
• Respects the current user's Azure DevOps identity and project permissions.
• Opens work items, queries, and dialogs within the Azure DevOps experience.
• Stores Insights, Roadmaps, and project configuration through the Azure DevOps Extension Data Service with project-scoped collections.

The result is a familiar workflow: configure a view where needed, then return to the same Azure DevOps pages and work items your teams already know.

Who is it for?

Trajektori is intended for:

• Product owners who need a release-oriented view of delivery.
• Portfolio and program managers coordinating several teams or projects.
• Delivery managers who need a dependable timeline and progress view.
• Project administrators who configure fields, columns, and project-specific defaults.
• Teams that want flexible reporting without copying work item data to another system.

It works especially well when different projects share a broad planning goal but use different fields, iterations, filters, or delivery conventions.

Getting started

After installing the extension:

1. Open Trajektori from the Azure DevOps project or organization context.
2. For Releases, ask a Project Administrator to confirm that the project has a Release work item type and the Custom.ReleaseId field.
3. Create an Insight or Roadmap and select the projects, fields, date source, and filters that match your process.
4. Save the view and share its Azure DevOps link with the people who need it.

The extension uses the current Azure DevOps project context. Users need access to the relevant projects and work items for data to appear in a view.

Permissions and data

Trajektori requests the Azure DevOps scopes required to read and update work items and to resolve user and project information:

• vso.work
• vso.work_write
• vso.graph

Trajektori uses Azure DevOps authentication and the permissions of the signed-in user. It does not replace Azure DevOps permissions: users can only work with data and actions allowed by their Azure DevOps access.

Insights, Roadmaps, and related project configuration are stored using the Azure DevOps Extension Data Service in project-scoped collections. Work item data remains in Azure DevOps.

Built for clear decisions

Trajektori connects the operational detail of Azure DevOps work items with the views people need for planning and review. Releases show what belongs together. Insights show how work is distributed. Roadmaps show when it is expected to happen.

All three capabilities remain configurable, project-aware, and close to Azure DevOps standards so teams can gain a broader view without losing the familiar way of working.

Learn more

Discover Trajektori and its approach to portfolio and delivery management at trajektori.nl.