Make the terminology around "Organization" customisable
Across most of Aha! you are able to re-name key items, such as Objectives, Epics, Ideas etc... this is great as it helps you align to the terminology used inside your company. It is not currently possible to do this for Organizations. I believe it...
Dan Jeffery
about 2 years ago
in Account settings
0
Future consideration
We have many workspaces that would benefit from the ability to add pages and views to the top nav. For our use case, we would like to: Add sub pages to existing top nav items Add new top nav items to create a folder of quick links We do not have a...
Once a prioritized list is created/saved, it would be useful to be able to bulk edit the Epics & Features contained in the saved Prioritization list. Assign tags, goals, initiative, dates, etc. to help with tracking, reporting and filtering vi...
Chris Lenzo
over 1 year ago
in Features
1
Future consideration
We can require fields upon a records creation with the create record layout. But to complete a record, users just need to change the status to a status in the Shipped category. However, completing a record sometimes requires other fields to be upd...
Erik Johnson
over 3 years ago
in Account settings
0
Future consideration
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi
about 5 years ago
in Jira
2
Future consideration
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck
almost 6 years ago
in Pivotal Tracker
1
Future consideration
Who would benefit? All Product & Project managers who need an additional level of organization to do "feature" level releases. This is especially useful since we train & speak to feature level releases in Agile framework & have no actu...
Leslie ORegan
9 months ago
in Features
1
Already exists
Aha! Develop: Extend the work data model to have a layer below requirements
In Roadmaps, currently using all of the record types for work in the data model (initiatives > epics > features > requirements). This is integrated with ADO, however, in ADO there is one layer below requirements (PBIs) called "Tasks". Thi...
Dale Potter
over 1 year ago
in
0
Future consideration
Based on trends we have seen with idea submission, there is generally a few buckets submissions fall into that require an Admin Response. As such, we have drafted positioning templates to expedite a proper response in these situations. It would be...
Guest
over 3 years ago
in Ideas portal
0
Future consideration
Currently each custom field, e.g. in Feature detail is listed in an extra line.
The fields are very short, so a lot of unused space is wasted right of the fields.
It would be very helpful to arrange the custom fields the same way like it is possib...
Alexander Vukovic
over 6 years ago
in Features
1
Future consideration