When assigning To-Dos to someone, it'd be useful to know how much time they're spending on it, rather than just Done/Not Done. That could be rolled into the feature/requirement/etc's time estimates, too. This would need to be enterable by Reviewers.

I understand that Features are not to be touched by Reviewers, but User Stories are items that typically get assigned to non-product managers. It would be extremely useful to allow Reviewers to log time on Requirements, so the Product Manager can ...

Contributors or another role should have the capability to edit selective fields (ie Internal Notes or Description) vs all fields like the product owner. By default, the field should be editable by the product owner, but there should be a setting ...

The new Roadmap "Starter" report is very cool way to visually build roadmaps against multiple products. However I would not call this a report, this is a missing functionality to the releases section. This feature needs the ability to visually dr...

We have an internal feedback portal where people from various teams (Sales, CS, Support, AMs) post their ideas and feedback for our product. Our product team can't keep frequently checking the workspace for new Ideas added. So the product team nee...

Need to generate a sensitive real-time report that only specific individuals have access to. Not access by product (to inclusive) and not by password (as that can be shared).

We have initiatives at the company level that represent large investments across multiple products. We'd like to be able to associate this initiative directly to saved reports that are associated so that we can centralize & standardize the ent...

What is the challenge? There's currently no way to sync feature dates in their entirety to Trello. Aha's current integration only surfaces Trello's Due date for mapping, meaning that it's impossible to do do time-based planning across platforms as...

When grouping by assignee, the view is limited to 50 users. Not 50 users at a time, but 50 users total. The truncation seems to be arbitrary as well, rather than picking, say, the first 50 users. I was informed that this is for performance reasons...

The status from devops should automate the status of the feature or requirement in Aha!