Calculate progress from both requirements and to-dos combined

Teams often track both requirements and to-dos within a feature or epic, but the current progress calculation options force you to choose between tracking one or the other. If you select "Calculate from requirements completed," your to-dos are ignored in the progress calculation, and vice versa.

This creates an incomplete picture of actual work completion, especially when teams use requirements for defining "what" needs to be built and to-dos for tracking "how" it gets done.

Users must either manually adjust progress or accept that their progress metrics don't reflect all the work being tracked.

Inaccurate progress reporting leads to poor visibility into actual feature completion status for stakeholders, portfolio managers, and team members.

This can result in missed deadlines, incorrect prioritization decisions, and a lack of confidence in the reporting data. Teams may spend extra time manually updating progress or creating workarounds, reducing the value of using both requirements and to-dos as intended.

For organizations that rely on Aha! for roadmap accuracy and status reporting, this limitation undermines trust in automated progress tracking.

Add new progress calculation options that combine requirements and to-dos:

• Calculate from requirements and to-dos completed: Progress based on the completion of both requirements and to-dos (weighted equally or by count)

• Calculate from requirements, to-dos, and all dependents completed: Includes all dependent items from both categories for a comprehensive view

Optionally, allow users to set weighting (e.g., requirements count for 70% of progress, to-dos for 30%) to reflect the relative importance of each work type. This would give teams accurate, automated progress tracking that reflects all the work they're managing in Aha!.