The columns shown are interesting, but not particularly useful to me. I'd like Timeframe, Goal, Progress, and Status. I suspect other users would find it useful as well, perhaps with other content and layout requirements.
Guest
12 months ago
in Strategy
0
Future consideration
Who would benefit? anyone trying to report data in tables What impact would it make? could add as many fields as needed, as well as have the column width necessary How should it work? Currently, in notes, the table can only be as wide as the viewa...
Jennifer Lange
6 months ago
in Notes
0
Future consideration
Don't Send Scheduled Reports if Report Doesn't Meet Criteria
Who would benefit? Anyone receiving schedule reports What impact would it make? Reduced inbox clutter How should it work? Allow users to only send scheduled reports when it meets some sort of criteria. As an example, we have reports that identify ...
Matt Marino
6 months ago
in Reports
0
Future consideration
Allow filtering of webhook events by custom fields
Who would benefit? Anyone using webhooks and custom fields What impact would it make? It would allow directed webhook events How should it work? I can currently filter webhook send events via selected activities on the standard set of fields. It w...
Guest
6 months ago
in Ideas
0
Future consideration
Filter search on Custom Table field within overview on an object.
Who would benefit? Anyone who uses custom tables to provide values. What impact would it make? It makes finding values simple How should it work? If I have a custom table like the following in image simple1.png it only allows me to search on the t...
Guest
6 months ago
in Strategy
0
Future consideration
Automatically include "Goal archived" or "Initiative archived" filter in strategy reports
Who would benefit? Anyone building reports that are based off goals or initiatives. What impact would it make? Save time and ensure completeness of reporting. How should it work? When creating a list/pivot/custom roadmap report that starts with go...
Madeleine Black
6 months ago
in Reports
0
Future consideration
I've wished for a couple of different Kanban views that don't yet exist in Aha! and Aha! support has recommended I build a pivot table to at least get a static view of the Kanban I want. Sometimes that static view is enough, but sometimes I really...
Peter Marshall
almost 8 years ago
in Reports
9
Future consideration
The Parking Lot needs beefing up. If you have a lot of granularity to your Parking Lots (created Parking Lot A, Parking Lot B, ... Parking Lot Z) it gets hard to us UX wise. The gray expandable box on the Board view resulting in lots of scrolling....
Guest
over 8 years ago
in Releases
4
Future consideration
When two record types are linked through a "Record relationship" custom field, all standard/custom fields from both records types should be available for selection in reports
Use case: Organizations are used to track customer information. We have created a record relationship custom field (type: organizations) on epics and features to specify customers the work will impact. Challenge: When building list/pivot/chart/cus...
Dale Potter
over 1 year ago
in
0
Future consideration
We use Assembla for issue tracking and Aha! for Roadmapping. Ideally the two products would be linked to tie roadmap features and milestones to Assembla.
Guest
over 9 years ago
in Wanted
13
Future consideration