/
Resolved Support Case: Incorrect Remaining Estimate Values in BigPicture Cloud Resources Module

Resolved Support Case: Incorrect Remaining Estimate Values in BigPicture Cloud Resources Module

This article documents a resolved support case involving incorrect remaining estimate values displayed at the skill level when using the 'Teams / Skills' grouping in the BigPicture Cloud Resources module.

Outcome: The issue was a regression bug reintroduced in a newer version. It was resolved by a backend fix applied by the development team.

Issue summary

A customer using BigPicture Cloud reported that the Resources module incorrectly displayed remaining estimate values at the skill level when using the 'Teams / Skills' grouping. The values at the skill level were identical to the team total rather than showing the correct per-skill breakdown. The 'Skills' swimlane alone calculated correctly.

Symptoms observed

  • In the Resources module with 'Teams / Skills' grouping, the remaining estimate at skill level showed the same value as the team total.

  • The 'Skills' swimlane calculated values correctly when used independently.

  • The issue was a recurrence — it had previously been fixed but reappeared after a new release.

  • The issue was confirmed working correctly on March 19, 2026 and broken as of April 8, 2026.

Root cause

The issue was a regression bug in the Skills/capacity calculation feature. A previous fix (rolling back the new calculation logic) had resolved the issue, but the v8.71 release reintroduced the faulty aggregation logic for the Teams/Skills grouping view.

Resolution

The issue was escalated to the development team, who applied a backend fix. The customer confirmed the issue was resolved the next day without any action needed on their side.

How to troubleshoot similar cases

  1. Verify the grouping mode — Check if the issue only occurs with 'Teams / Skills' grouping or also with 'Skills' alone.

  2. Compare values — Confirm that skill-level values match the team total (indicating aggregation bug) vs. correctly showing per-skill breakdown.

  3. Check version history — Look for recent updates that may have reintroduced known bugs.

  4. Search for related tickets — Check if the same issue was reported and fixed previously (regression pattern).

  5. Escalate to development — If confirmed as a backend calculation bug, escalate with HAR files and screenshots.