Who would benefit? All What impact would it make? Better usability How should it work? In using the new Now, Next, Later Roadmap, here's some feedback: Its appearance is bland. I'd expect more control of the card layout, similar to workspaces, wit...
Jeff Broderick
about 1 year ago
in Roadmaps
6
Shipped
To-dos assign work to other people (or with work requests, other workspaces), ranging from minor tasks to workflow approvals. To drive consistent workflows, it would be great to be able to create templates for to-dos, much like we can for initiati...
Synchronize Ranking from new Prioritization view to other Aha! areas
I’m just playing around with the new prioritization list for Features and Epics ( https://www.aha.io/support/roadmaps/strategic-roadmaps/features-and-activities/feature-prioritization-page ) and I wondered: if the rank changes in that list due to ...
Stephanie Redl
over 2 years ago
in Features
14
Shipped
Is it possible to create custom fields at the requirement level? For example, we want to set prioritization at the requirement level that will push into JIRA. We would want to create a custom field for this.
Allow capacity report to be configured using story points
We are a mature Agile team that uses story points exclusively to estimate the work done in each sprint.
The new capacity report feature rollout is excellent, but it does not allow for story points to be used as the method of estimation for a sprin...
Would be great if Aha was mobile friendly. That way we can log time, update our notebooks, see what we are working on in a current sprint etc on the go.
Ideas portals should not show ideas from other portals that share the same products
If you create two private (or public) ideas portals and both have product A and product B, any ideas created in either portal are visible in the other.
In this scenario, I want one portal for employees and one for customers. I do not want custome...
Make success metric field optional and/or remove field from Goals layout
Similar to every other field on a Goal record, I would like to be able to remove the ‘Success Metric’ field and/or make it optional on the create screen.
Often when new Feature requests come in they are at, what we consider to be the Master Feature level...basically an Epic. For future releases, we hold a Release Planning session where our engineers apply high level estimates to Master Feature that...
This idea is to update capacity for teams to support the ability to estimate in story points. You are currently only able to estimate in hours, people, or cost.