Idea portal public status should remain as last public status if next status is hidden
There is no point in having internal/external visible status workflow if the external user is shown no status to an idea that is visible if the idea is going under a multi-step internal review process (which is the function of having an internal/e...
Laura Giles
about 6 years ago
in Ideas portal
0
Future consideration
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
You might probably not want to go down that route, but it could be nice to have some kind of light CRM functionality as well. Companies, contacts, notes etc. Especially as people communicate with outside world, it will be very beneficial to know w...
Guest
about 6 years ago
in Application
0
Unlikely to implement
I have my feature tiles configured with a certain layout and when I’m in the feature detail view which gives me more room to write requirements while focusing on a specific release, the tiles still show the default layout and not the configured la...
Andrew C
about 8 years ago
in Features
2
Already exists
It would be nice to filter (AND, OR, NOT, etc) for specific pre-set tags within a custom field. For example, if I got a custom field called NUMBERS. Within that field I've pre-defined "1", "2", "3", "4". These numbers are assigned to a requirement...
Simon Au
about 4 years ago
in Reports
0
Future consideration
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
about 4 years ago
in Jira
0
Future consideration
Report on records related directly and indirectly to another record
Example use-case/problem... Features may be associated to an initiative directly, through a release, through a master feature, through another initiative, through a dependency, etc.; but there is no way to view all features associated to an initia...
Guest
about 6 years ago
in Reports
0
Future consideration
Add a link from Features > Details page back to Releases > Details page
When I am looking at a particular Feature on the Details tab (e.g. a page of the form: https://yyy.aha.io/features/XXX-123), there is no quick way to link back to the Releases Details tab that this Feature resides in (e.g. a page of the form: http...
Nick Mariette
about 8 years ago
in Features
0
Already exists
Enable the Drawer and Details layouts to be different
Add flexibility to modify the Details layout and Drawer layout separately. At the moment, when shifting the fields up and down on the drawer display, the same top-down list is applied on both views.
Mark Slykhouse
about 4 years ago
in Features
0
Future consideration