What is the challenge? we import releases from Github Milestones which have no start date meaning the date range on releases is incorrect. What is the impact? results in releases on roadmaps which have inaccurate (infinite) bars and require manual...
Guest
6 months ago
in Releases
0
Future consideration
Who would benefit? Align terminology with what we use it for Early adopter/BETA What impact would it make? Make it easier for the team to adopt it How should it work? Custom terminology like other aha! features.
Ability to tie color feature color to other fields
Status doesn't help to organize we would rather color code based on priority. We created a custom field for this and are eventually planning to use scorecards. We would like the ability to tie the color of the feature card to other fields beyond s...
Nick Galassi
over 6 years ago
in Features
15
Future consideration
That we can only have End-to-Start Dependencies drawn is causing issues with our program Overviews. Our Managers are concerned by all of the red. Please enable us to also include Start-to-Start Dependencies, and Start-to-End Dependencies. If we ca...
Guest
over 2 years ago
in Features
4
Future consideration
Ideas Portal custom fields that are only visible to Employees/Partners or higher
Currently (as far as I can see) you can only set custom fields in the Ideas Portal to be public (all logged in users) or private (AHA users). There isn't the ability to hide a field from the public and only show it to Employees/Partners or AHA use...
Andrew Badge
almost 9 years ago
in User management
4
Future consideration
It would be useful to define default Document Access settings for notes/whiteboards at parent line levels to be inherited down to workspaces instead of needing to make setting changes for each workspace individually
Jeanette Resnikoff
about 1 year ago
in Notes / Whiteboards
0
Future consideration