Allow Aha base field values to be set based on custom worksheet fields
Custom worksheets and the fields within them allow powerful formula-based derivation of values but the base Aha fields in many cases allow certain things to be driven across the application. For example, the capacity field in releases or estimate ...
As an product owner, I want idea portal submitters/users to have a simple, obvious, and fast method to share a link to an idea when they have just created it, or are viewing any idea, so that they can push the link to other in the organization thr...
Dan Molloy
about 4 years ago
in Ideas portal
0
Future consideration
Add Product ID as a field to the Workspace Info Tab
The only way users can see the workspace Product ID is to pull a report. As a result, our workaround is to download the Product ID and upload it to a custom field on the workspace layout. This is a lot of manual work for something that is inherent...
Cindy Datlof
about 4 years ago
in Account settings
4
Unlikely to implement
A way to identify and address discrepancies between items in Aha! and Jira
It is quite impossible to manage the Features and Requirements integration with Jira. There seems to be multiple ways of braking the synchronization between the items in Aha! and Jira, like:
- Deleting items in Aha! do not get deleted in Jira.
- C...
Ragnar Wessman
almost 7 years ago
in Features
1
Unlikely to implement
Currently, when a mockup is updated or deleted, the file does not stay in sync with an integrated system. Ideally, the same mockup file would continue to get updated across the systems.
Option to filter out archived timeframes and releases on Overview page for new experience
In the new workspace overview tab, there are filters to show all, in progress, not started. It would be useful to also be able to filter out archived timeframes so not all goals and initiatives are showing so the context for "all" is set to the cu...
Ronnie Merkel
about 4 years ago
in Application
1
Future consideration
Use pagination to remove 50-user limit in Workflow view
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...
Guest
about 4 years ago
in Features
2
Unlikely to implement