ADD A NEW IDEA

All ideas

Showing 5905

Allow setting proxy vote view layout fields to Read Only

What is the challenge? Some record layouts in Aha! allow for setting fields to Read Only on the View version of the layout so they cannot be edited further after they are created. The layout for proxy votes does not allow this. What is the impact?...
Maria Plotkina about 2 months ago in Ideas 0 Future consideration

Report on a values historic values

Enable the user to report on the values of a field based on its history. maybe a calculated field property where you indicate the field and the version back for that field. History(Custom_Field1,1) would show the value of that field one change bac...
Steve Podzamsky about 4 years ago in Reports 5 Future consideration

Show child initiatives nested under parent initiatives on the strategic roadmap

We have initiatives with child initiatives and those child initiatives contain releases, epics and features. The child initiatives are in a separate workspace line from the parent initiatives. The Strategy>Initiatives>Roadmap view works fine...
Dave Tucker almost 3 years ago in  2 Future consideration

Allow formatting and wrapping text on chart labels

I never use Aha charts in our internal reports because the labels display poorly. It's a shame, because it prevents our org from more fully adopting Aha. I export everything to do reporting in a Spreadsheet simply because the labels are unhelpful ...
Guest almost 2 years ago in Reports 2 Future consideration

Multi-language support in KBs

What is the challenge? Non-English speaking users need to access content in a KB. Currently a separate KB must be generated in each applicable language. How would you solve it? Provide KB translation. What impact would it make? Allow non-English s...
Emily Yankush 7 months ago in Knowledge base / Notes 3 Future consideration

Show more context for added/removed records in retrospective report

I want to understand more about the records that are added to or removed from a release: When was it removed? Where was it moved to? What is its current status? I would like to see this information in the retrospective report
Jeff Tucker about 1 year ago in Reports 1 Future consideration

Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)

Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
Hank Liu 8 months ago in Epic 0 Future consideration

MS Planner integration

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...
Guest over 5 years ago in Wanted 8 Future consideration

Dependency roadmap as a standard view

Who would benefit? Users that: need to track upstream work they are dependent on need to understand downstream work that is dependent on their work need to easily identify delivery risks based on dependencies What impact would it make? A roadmap i...
Dale Potter 11 months ago in Dependencies / Roadmaps 0 Future consideration

Allow Release Date (internal) and Release End date (date range) to sync

Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
Bonnie Trei 10 months ago in Releases 1 Future consideration