Allow aggregating multiple Jira stories into a single Aha! requirement (summary sync option)

What is the challenge?

• The Aha!–Jira integration requires a 1:1 sync between Jira stories and Aha! requirements. For teams managing large epics, this creates excessive noise in Aha! and makes it difficult to maintain clean, high-level views for portfolio and leadership reporting.

What is the impact?

• Features become cluttered with low-level execution detail, reducing usability and clarity for stakeholders. Teams either over-sync (creating noise) or turn off story sync entirely (losing visibility), leading to inconsistent processes and weaker reporting.

Describe your idea.

• Introduce an optional setting to aggregate multiple Jira stories into a single Aha! requirement (summary record). This requirement would roll up key data (status, progress, story count) while linking back to Jira for details. This allows teams to maintain clean, high-level visibility in Aha! while keeping execution detail in Jira.