What is the challenge? Reports can be set to be editable by anyone who has access. This is necessary in many cases, but it is not possible to see when someone has edited the report. What is the impact? If a report has been changed, you cannot find...

What is the challenge? Currently, filters don't work when Now, Next, Later (NNL) reports are shared as webpages. What is the impact? Without filtering capability in shared NNL reports, recipients cannot customize the view to focus on specific data...

Who would benefit? Teams using OKRs that choose to associate work with Key Results rather than the Objectives What impact would it make? More logical display of strategy through the new OKR records in the Hierarchy report How should it work? Abili...

Details & Business Problem Within the prioritization view, an automated prioritization re-rank by filtering out items that are "done" or "will not implement"; ranked numbered list automatically adjusts to the records that have been filtered...

as a user, I want to be able to include the story map (Name, Description and Step, step sequence) to any report and report type, so that I can group my reporting by the story map information.

Today, if the detailed estimate is 0 then the Initial estimate is ignored in the best estimate calculation. I would expect us to ignore null/zero detailed estimate values if the initial estimate is >=1 when calculating the best estimate.

Related to: https://big.ideas.aha.io/ideas/APP-I-2911. It would be great to have the option to bulk delete integration links for features in Aha. For example when you know the corresponding issues in JIRA don't exist anymore.

What is the challenge? Currently, when searching in the Knowledge Base, only the current page is shown, along with Previous and Next buttons. Users have no visibility into how many total result pages exist. This created several challenges: U...

What is the challenge? We can't import requirements into Aha What is the impact? Causes manual entries Describe your idea Allow bulk import of requirements

I think todos have a lot of potential to represent non-feature work across Aha. I like the idea of not "polluting" aha with workarounds where features are used to represent work, nor requirements used to represent non-feature related work. There i...