We update hourly rates on an annual basis. The Teams we define span Scenarios so we need to be able to define an hourly rate by Scenario for a Team. This functionality will enable flexibility in cost reporting and forecasting.
Chris Brooks
over 4 years ago
in Capacity planning
0
Future consideration
We need an ability to assign one or more individuals to an Aha! record and indicate that their capacity is partially allocated to that record. For example, initiative A is estimated at 1,700 hours and assigned to Team A. User A on the team is assi...
Aha! data model support for actual features / components / themes, rather merely work output
Currently the "features" and "master features" relate to work output, not actual product concepts that users care about.
tl;dr; please give us more ways to separate concepts from the actual work. Features should technically be conceptual, and shou...
Guest
over 5 years ago
in Features
0
Future consideration
Who would benefit? Product Managers What impact would it make? Save time and duplicate effort creating our own template How should it work? Demographic trends: What is the current or changing population distribution of the consumer base within you...
Guest
about 1 year ago
in Notes
0
Future consideration
Who would benefit? Product owners, stakeholders What impact would it make? It would make my job more efficient as I would know when someone added something to a shared note. Currently I have to constantly refresh or go back to the shared note to m...
Jennifer Lange
about 1 year ago
in Notes
0
Future consideration
Allow scheduled delivery of reports to non-Aha users
We have others in our organization that need to see the summary Aha data, in .csv format, on a daily basis. This is allowing us to do advanced reporting. I will need to forward these reports every day to the desired recipient list.
Sara Olson
over 2 years ago
in Reports
0
Future consideration
User Story map should support epics that span columns
I created a user story map with multiple columns, each for one activity in my flow. Now I want to pull features from multiple columns into an epic and move into JIRA. However, as soon as I assign to a master feature, the user story map pulls the f...
Ashwin Jeyakumar
over 4 years ago
in User story map
0
Future consideration
The default assigned colours for releases can often be very similar to each other. Being able to manually updated them will help with clarity of the view and also support teams with visual impairments/colourblindness.
Steve Dagless
over 4 years ago
in Releases
0
Future consideration
While many To Dos are simple and can be quickly marked off. Some could be longer and do not work as "requirements. Would be nice to set a start date and end date on a To Do and perhaps spark a notification reminder to "get started".
Carolee Snarr
over 3 years ago
in To-dos
1
Future consideration
I would like to be able to limit use of an extension to a set of users. For example, if I have an extension to deploy code to production, I would like to limit it so that only an ops team and team leads can trigger it.
Justin Weiss
over 3 years ago
in Extensions
0
Future consideration