Ability to do subtotals in Pivot tables (in addition to Grand Total as it is today)
For ex: if we have a dollar value (numeric custom field) associated with each release, let's say it's the release cost - I would like to be able to add up all release costs per each product (sub-totals) in the same product line, in addition to the...
Guest
almost 8 years ago
in Reports
5
Future consideration
Show description in one to many view for custom tables
What is the challenge?
When using a one to many relationship for a custom table on an Aha record users will create entries on that tab. This view does not show more information about the fields from the "details" section in the field editor.
...
Julia Pence
3 months ago
in Roadmaps
0
Future consideration
Bulk load a list of requirements or To Do assignments
What is the challenge? Have long lists of requirements or To Dos to add to a feature card or project; including the assigned person, requirement name, description, and the due date. What is the impact? Save data entry time for project management D...
Carolee Snarr
10 months ago
in Features
0
Future consideration
Support custom fields on portal users both for regular and sso login
We need to track several pieces of metadata about a user to effectively understand their request. This metadata is intrinsically associated with the user and cannot change from idea to idea. This includes things like the user's role in our custom ...
Guest
about 5 years ago
in User management
1
Future consideration
What is the challenge? When moving from a ZenDesk knowledge base to an Aha! knowledge base, currently each document must be uploaded to Aha! individually. What is the impact? This would improve the speed for migrating tools. Describe your idea Add...
Emily Yankush
about 1 year ago
in Knowledge bases / Notes
0
Future consideration
It would be great if, instead of just showing the underlying value, the scorecard metrics could use abstract labels... for example, for an 'effort' metric we might use t-shirt sizes such as "Small", "Medium", "Large" and "X-Large" behind the scene...
Guest
almost 10 years ago
in Features
6
Future consideration
Rename product value field in non-product workspaces
The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.
Austin Merritt
over 3 years ago
in Features
2
Future consideration
Utilize Tags Across All Areas (Releases, Ideas, & Features)
Right now, you cannot use the existing default "Tag" field (used in ideas & features) within release layouts. If I want to add tags to a release layout, I have to create a custom tag field and cannot re-use any of the existing tags that were c...
Connor Shay
about 8 years ago
in Releases
5
Future consideration
Make it easier to follow a dependency line in a whiteboard
What is the challenge? If you add a lot of lines to a whiteboard they can be hard to follow. What is the impact? This can make whiteboards confusing and hard to use. Describe your idea If you click a line it would highlight the line and make it st...
Chris Quigley
about 1 year ago
in Whiteboards
0
Future consideration
In my scenario, there are times that a feature is in a given status, and as a result, I would want that feature to move to a different release. For example, If I abandon a feature, I want it removed from a release and put into a parking lot where ...
Jerrold Emery
almost 3 years ago
in Account settings
2
Future consideration