Azure DevOps Time Tracking Extension

The OnePlan Azure DevOps Time Tracking Extension, available on the Azure DevOps Marketplace, provides a seamless way to integrate strategic planning and agile execution. This extension embeds OnePlan directly within Azure DevOps using secure Iframes, allowing users to view and interact with OnePlan content — such as portfolios, plans, and resource data — without ever leaving the Azure DevOps environment.

By using Iframes, the extension enables real-time access to OnePlan capabilities from a dedicated tab within Azure DevOps projects or work items. This ensures that development teams, project managers, and product owners can stay aligned and work efficiently across tools — all while maintaining secure, role-based access to OnePlan data.

Key Benefits

Centralized Work Management

View and manage OnePlan portfolios, programs, and plans right from Azure DevOps — ensuring your developers and project managers are always aligned.

Enhanced Visibility

Bring planning and execution data together in one view. Project managers can track real-time updates from development teams without leaving OnePlan, while engineers stay focused on Azure DevOps.

Streamlined User Experience

The Iframe-based integration minimizes disruption to your team’s workflow. It feels like part of the Azure DevOps environment, while securely connecting to the full power of OnePlan.

Secure

Leverages your organization’s authentication policies with Entra ID Single Sign-On support. Admins can configure which OnePlan pages are accessible via the Iframe for optimal usability.

How it Works

The OnePlan Azure DevOps Time Tracking Extension enhances your Azure DevOps environment in three key ways once installed:

1. Project Navigation Panel Integration - The extension adds a OnePlan link in the left navigation panel of every Azure DevOps project across your organization. This link opens a configurable Iframe that displays OnePlan content — such as portfolios, plans, or dashboards — tailored to the context of your organization’s planning needs. This makes OnePlan easily accessible from any project without requiring separate logins or tabs.
2. Work Item Tab Integration - The extension also adds a dedicated OnePlan tab inside Azure DevOps work items or project views. This embedded tab uses a secure Iframe to show relevant OnePlan pages (e.g., plan details, resource plans, or status reports) directly within the Azure DevOps UI, giving users fast access to planning and portfolio data while staying focused on delivery work.
   1. In Azure DevOps, if the Work Items have not yet been brought into OnePlan, an event will automatically trigger to import the items into OnePlan once the OnePlan tab is clicked.
3. OnePlan Worklog Section - The extension adds a section titled OnePlan Worklog to the Details tab of all work items in Azure DevOps. 
   1. This section is automatically displayed for any work item type that is included in the integration configuration to be imported into the OnePlan Work Plan. 
      1. Date (Calendar Field): Specifies the date the work was performed.
      2. Hours (Number Field): Specifies the amount of time worked for the selected date.  
   2. When time is entered in these fields, the data is captured and imported into the corresponding timesheet in OnePlan. The timesheet entry is attributed to the user who submits the timesheet data in Azure DevOps, not to the user assigned to the task in Azure DevOps. This ensures accurate tracking of individual user submissions and proper reporting within OnePlan. 
      1. The user is still responsible for submitting their complete timesheet in OnePlan for all relevant entries for that week or time period.

Technical Details

Setup Prerequisites

• Active OnePlan and Azure DevOps integration subscription in my.oneconnect.ai or in eu.oneconnect.ai
• Azure DevOps project permissions to install and access extensions
• OnePlan group has Timesheets available, create time periods for your OnePlan group. 

Extension Installation

1. User must be an Azure DevOps Organization Owner (or have permissions to install extensions), and have access to the Azure DevOps Marketplace.
2. Once logged into Azure DevOps navigate to https://marketplace.visualstudio.com
3. In the search bar, type “OnePlan".
4. Click on the OnePlan extension labelled “Time Tracking for Azure DevOps”.
5. Click “Get”.
6. Select your Azure DevOps Organization from a dropdown.
7. Click "Install”. Azure DevOps will redirect you to the selected organization.
8. Confirm the extension is being added to the correct Azure DevOps Organization.

After Installation

Once installed:

1. A OnePlan extension will appear in the left navigation of every project across the organization.
2. The OnePlan tab will be available within individual work items.

How the Azure DevOps Extensions Select an Integration

The Azure DevOps extensions automatically determine which Azure DevOps integration to use based on the integrations configured in your OnePlan environment.

If You Have One (1) Azure DevOps Integration

If only one Azure DevOps integration exists in the environment, the extension will use that integration automatically, regardless of whether the integration is enabled or disabled.

If the extension is not functioning as expected, verify that the integration is enabled.

If You Have Two (2) or More Azure DevOps Integrations

When multiple Azure DevOps integrations exist, the extension follows this logic:

• If no enabled integration has Use this integration in the ADO DevOps Extension selected, the extension will use the first enabled integration it finds.
• If multiple enabled integrations exist, this can cause the extension to connect to an unintended integration.

To specify which integration the extension should use:

1. Open the desired Azure DevOps integration configuration.
2. Expand Azure DevOps Advanced Options section.
3. Enable the checkbox labeled Use this integration in the ADO DevOps Extension.
4. Save the integration settings.

It is recommended that only the intended integration has this option enabled to ensure the extension connects to the correct Azure DevOps instance.

Understanding Time Tracking and Timesheets

The Azure DevOps Time Tracking Extension uses the OnePlan Worklog form to create entries directly in the OnePlan Timesheets module.

Time Entry Process

When a user enters time in the OnePlan Worklog section of an Azure DevOps work item and saves the entry:

1. A timesheet line item is automatically created in the OnePlan Timesheets module.
2. The time entry is associated with the user who submitted the worklog entry.
3. The timesheet line item is created in an Unsubmitted state.

Entering time in Azure DevOps does not automatically submit or approve the timesheet. Users must still complete the standard OnePlan timesheet process.

Required Timesheet Workflow

For time to be reflected throughout OnePlan, the following process must occur:

1. Enter time using the OnePlan Worklog form in Azure DevOps.
2. Submit the corresponding timesheet in OnePlan.
3. Have the timesheet approved (if approvals are enabled).

Only after this process is completed will the time be available for reporting and updates within OnePlan Resource Planning and Financial Planning modules.

Child Tasks vs Parent Tasks

The OnePlan Worklog form allows users to enter time against any synchronized Azure DevOps work item that is mapped to the OnePlan Work Plan. However, users should understand how OnePlan calculates Timesheet Hours within the Work Plan.

The Timesheet Hours field in OnePlan is designed to roll up hours from child work items. As a result:

• Time entered against a child task will contribute to Timesheet Hours calculations and rollups.
• Time entered directly against a parent task will appear in the Timesheets module but will not be included in the Timesheet Hours rollup shown in the Work Plan.

This behavior is by design and ensures that rollup calculations are based on the detailed execution work being performed at the child-task level.

Best Practice

For the most accurate reporting, resource planning, and financial tracking, users should record time against the lowest-level work items (child tasks) whenever possible.