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
almost 7 years ago
in Features
1
Future consideration
For a release, you can add a feature to a phase to enable an understanding of how far through a release a feature is. The phases defined are relevant to that release.
A 'product' release can be attached to a master release. This is likely to be a ...
Guest
almost 7 years ago
in Releases
0
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
about 6 years ago
in Pivotal Tracker
1
Future consideration
Allow exporting calendar bookmarks to Google Calendar/Outlook/3rd Party Programs
We use external tools to track when certain members of our team are available/unavailable. It would be great to not schedule releases of features when that person will be out, and it would be great to see dates generated within Aha! within those t...
Guest
almost 7 years ago
in Reports
0
Future consideration
As a security manager and Aha! administrator, I'd like to be able to disable attachments from being sent in emails to ensure that security policy is followed and that all content shared in/via Aha! requires a login.
Scott Goldblatt
over 7 years ago
in Account settings
0
Will not implement
Set the TFS Iteration and Area path per feature or requirement
Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
Jonathon Leeke
about 9 years ago
in Integrations
6
Already exists
Ability to copy entire workspace contents to another
After messing up in a workspace configuration or design, I find it very useful to have a one stop shop button to copy entire contents (including user story maps, personas, roadmaps, features, etc.) from one workspace to another.
Todd Materazzi
over 1 year ago
in Application
0
Future consideration
Part of the value of Aha! Roadmaps is making product managers look like rockstars. The platform could help make that even more explicit by providing an annual review they can generate at any time. This could be something like a dashboard with AI-p...
Reilly O'Connor
over 1 year ago
in Reports
0
Future consideration
Workspace reporting - add in information from child records
We maintain a large number of products and our CPO has mandated that all products have an initiative for a particular type of work. We use custom fields against initiatives to categorise our work and whilst we can apply a filter to identify which ...
Sophie Ramsden
almost 4 years ago
in Reports
1
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
over 5 years ago
in Jira
2
Future consideration