February 2026 Release Notes

• Governance Assessment: Fixed an issue where, when multiple governance models applied to a project, the model with the highest priority was not consistently used.

• Governance Assessments – Stage Gates: Fixed an issue where phase stage gate assessments did not correctly validate whether gates for prior phases had been completed.

• Governance Assessments – Funding Comparison: The Project Total Cost to Project Funding assessment now correctly applies the project setting (above-the-line or below-the-line financials) when comparing the full-year forecast with the budget.

• Exporting to Word and PowerPoint: Fixed an issue where the Project Type binding element returned blank data in Word and PowerPoint templates. A new binding element, {Project.ProjectType}, is now available.

• Status Report Export to Excel: Fixed a server error that occurred when exporting Status Reports to Excel from the project dashboard.

• Project Search: Searching for projects by end dates was returning the incorrect result set.

• Financial Cap Amort Export to Excel: Fixed an issue where the FYF flag incorrectly marked the first open month actual as Yes in the Excel export.

• Tier Project Property: The maximum character limit for the Project Tier property has been increased to 255 characters, allowing longer tier values to be stored.

• Exporting to Word and PowerPoint: Fixed an issue where the Program Word Report failed to generate when Generate Combined Report and Roll Up Promoted Sub-Projects were both enabled for programs containing sub-projects.

• Jira Integration: Fixed an issue where non–rich text Jira custom fields were not syncing correctly when mapped to rich text custom properties in Fluid. These fields are now supported and synced correctly.

• Task Editing: Fixed an issue where the cursor jumped to the end of the task title when editing tasks created via bulk import.

• Archived Project Export: Fixed an issue where exporting archived projects from the Financial Administration page returned an empty file.

• Project Details Bulk Edit: Fixed an issue where mandatory columns were not validated correctly during bulk edit.

• Expense Type Management: Fixed an issue where newly created expense categories were not available when creating new expense types.

• Export to Word or PowerPoint: Fixed an issue where Word exports were not generated for programs containing sub-projects.

• MS Project Upload: Updated the upload process to use each task’s unique ID. This allows users to save MS Project files using either Save or Save As without impacting the upload.

We’ve extended Below-the-Line (BTL) cost handling so it can be tracked separately without impacting project budget performance.

Previously, you could mark expense categories as BTL to split reporting totals (ATL vs BTL). However, BTL costs were still included in core project financials such as Full Year Forecast and Estimated at Completion (EAC) and therefore always contributed to variance vs budget/funding.

What's new

A new instance-level setting (configured once for the entire instance) now determines whether projects are allowed to exclude BTL costs from budget calculations.

• When this instance setting is OFF (default behavior):

  • BTL costs are tracked separately but still included in project total cost, Full Year Forecast, EAC, and budget variance (unchanged behavior).

• When this instance setting is ON (new capability):

  • Projects gain the ability to exclude BTL costs from their total cost and budget variance calculations.

When excluded, BTL costs:

• do not roll up into Full Year Forecast or EAC / Estimated Cost at Completion

• do not affect budget consumption or variance vs budget (because they’re not part of the “project total cost” used for comparison)

BTL costs are still fully supported for tracking:

• you can forecast them

• you can capture actuals (including via timesheets, if applicable)

• you can report them separately from ATL totals

How it works

1. Instance configuration (new)
   An administrator enables the 'Enable ATL/BTL Funding Reporting' setting that allows BTL costs to be excluded from project totals.

2. Expense category setup (existing)
   Expense categories are marked as Below the Line (BTL). All expense types under those categories inherit the same classification.
   

   

3. Project-level behavior (enabled by the instance setting)
   When the 'Enable ATL/BTL Funding Reporting' setting is on, each project gains a new control on the Project Edit page under Financial Management:

   Include Below-the-Line for Budget Variance

   This setting determines whether Below-the-Line (BTL) costs are included in the project’s total cost and budget variance calculations.

   • Yes
     Below-the-Line costs are included in project financials.
     Project total cost = ATL + BTL (same behavior as before).
     BTL costs contribute to Full Year Forecast, EAC, and variance vs budget.

   • No
     Below-the-Line costs are excluded from project financials.
     Project total cost = ATL only.
     BTL costs remain visible for tracking and reporting but do not affect Full Year Forecast, EAC, or budget variance.

   This allows teams to track indirect or non-budgeted costs on a project while keeping budget performance focused on above-the-line, funded costs.

   

   Please note that the flag is turned on by default, i.e. below-the-Line costs are included in project financials.
   

4. Project workspace
   When Below-the-Line exclusion is enabled for a project, the project workspace clearly reflects this in both summary metrics and financial tables.

   • Project financials summary
     The project financials summary displays a clear indicator such as “Excludes Below-the-Line Costs” to show whether Below-the-Line costs are included in or excluded from project total cost and budget variance calculations. If BTL costs are excluded:

     • All funding, variance, and margin metrics shown in this view are calculated using Above-the-Line (ATL) costs only. Below-the-Line (BTL) costs are not included in:

       • budget variance

       • Estimated Variance at Completion (EAC)

       • Full Year Forecast comparisons
         

   

   • Financial section
     In the financial breakdown:

     • Above-the-Line Totals are shown as a distinct subtotal, representing the costs that impact budget and variance.

     • Below-the-Line categories (for example, internal resource costs) continue to appear in the table with their own forecasts and actuals.

     • The overall Totals row still reflects all costs (ATL + BTL), ensuring full cost visibility, while budget and variance calculations rely on the ATL subtotal when exclusion is enabled.

   This makes it easy to:

   • understand which costs are driving budget performance

   • track indirect or non-budgeted costs without losing visibility

   • switch between an ATL-only budget view and a full cost view without duplicating data or projects

   

Use this when you want to track costs operationally but not treat them as consuming project budget. Common examples:

• Internal resource costs / timesheets tracked for utilization, but not funded by the project budget

• Overheads / allocations needed for visibility or finance reporting, but not part of the project’s controllable spend

• Chargebacks or indirect costs that shouldn’t drive “on/off budget” status

We’ve enhanced how date-based project phases work to make phase evaluation more consistent across governance and financial use cases, especially when phases overlap, fall mid-month, or interact with stage gates.

While date-based phases were already supported, this enhancement clarifies which phase truly applies on a given day, separates planned progression from governance constraints, and ensures consistent behavior across reporting and capitalization.

To support this, we’ve formalized the distinction between Nominal Phase (what the dates and phase order indicate) and Current Phase (what the project is actually allowed to progress to based on stage-gate completion). This gives PMOs and PMs clearer insight into why a project is in a given phase — and what needs to happen for it to move forward.

For full details and examples, (including overlapping phases, gaps, stage-gate blocking, and capitalization behavior), see the article How Date-Based Project Phases Work.

• Process Boards: Fixed an issue where collapsing a grouped backlog could intermittently cause a UI lock-up error.

• Timesheet Compliance Export to Excel: Fixed a query timeout that could occur when exporting the Timesheet Compliance Report to Excel.

• MS Project Upload: Tasks that are both pinned and set to auto-calculate are now imported with auto-calculate enabled only, as these settings cannot be applied simultaneously.

• Status Reporting: Fixed an inconsistency where the RAG status update character limit was fixed at 200 characters and not aligned with the Status Report Update limit. The configured status limit now applies consistently to both Status Report and RAG status straplines.