Concourse & Jira DC Portal


Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.


For immediate technical support, please follow this guidance to open a Service Now ticket.

Calculation Logic for ePro Rebuild

Put Simply Statement:
There needs to be calculation logic to take work item effort and run the correct order of operations to calculate effort hours from the Accelerator / Driver / Complexities assigned to each of the work items

We also need to decide where/how this calculation should occur as we are building this initially within the admin flow, and we will need to make it applicable to both User and Admin

Why it Matters:
We gotta be able to make the calculations work to make ePro give estimates!

What’s Needed:

  • Merge estimation and scoping modules into a unified interface.

  • Ensure real-time data sync between scoping and estimation components.

    • Work Item Data will be from a single point of reference so there will no longer be any eventing/syncing issues

  • Update permissions, navigation, and help documentation.

  • Early ACs:

    • Users can complete both scoping and estimation in one workflow.

      • Users can only Estimate after Scoping

    • No redundant data entry required between modules.

      • Work Item data is from single point

    • Changes in one area are instantly reflected in the other.

      • Same concept as inflight estimate resets

    • Users will need to have the same selection options as are currently available today in ePro

      • Project Size, Accelerators, Drivers, Complexity Matrix, Team Structure

  • Wyatt Lunson
  • Oct 23 2025
  • In Review