What is the challenge? Users who want to further customize their KB contents want more flexibility. What is the impact? This would give KB users more options in terms of the content they can add and how it is presented. Describe your idea Add the ...
Maria Plotkina
8 months ago
in Knowledge base
0
Future consideration
It will show sprints as a roadmap and will be able to give agile team more clarity.
This will benefit Agile / Scrum Teams.
A sprints view roadmap added to both Features and Release sections or once can select between timeline/calendar view or spri...
Guest
over 8 years ago
in Agile reports
10
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
10 months ago
in Epic
0
Future consideration
In Ideas portal, flexibility to provide conditional logic wherein dependency exists with an Epic/feature. We are using Ideas for leveraging Dependencies.
What is the challenge? Users create ideas, without there is a proper dependency What is the impact? Data discrepancies, because users omit to include dependencies to other records Describe your idea Allow conditional logic, to make mandatory depen...
Edgar Holguin
3 months ago
in Ideas
1
Already exists
Epic/Feature boards using custom fields than versions
What is the challenge? Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field...
Shiv Shankar Vedharajan
3 months ago
in Workflow boards
0
Future consideration
When cloning, please provide ability to clear values in custom fields before saving in Domain Epics/Epics
What is the challenge? User clone records, without cleaning the existing data that is not applicable for the new record. What is the impact? Data consistency and re-work Describe your idea Have an option, when cloning to reset all the other attrib...
Edgar Holguin
3 months ago
in Epic
0
Future consideration
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
Guest
about 6 years ago
in Releases
7
Future consideration
The current Aha! Kanban board does not provide the flexibility other tools such as SwiftKanban provide. Is there any plan to build an integration into Swift Kanban and/or is there any plan to build out a more robust kanban board within Aha! We hav...
Guest
over 5 years ago
in Application
5
Unlikely to implement
Knowledge base page publishes automatically once approved
What is the challenge? We want KB pages to be approved before they are published. What is the impact? It is a manual process right now and we have to trust users that they will not publish a page before all the approvals have been given. Describe ...
Aaron Weinberg
7 months ago
in Knowledge base
2
Future consideration