We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...
Adding features from initiatives or whole initaitves in the story map would make life a lot easier
you can add existing records from a releawse or by feature, but adding entire iniatives worth of features is not possible. It would be helpful to be able to do that
Guest
almost 2 years ago
in User story map
0
Future consideration
Handling Use Case of Features Tied to Company Initiatives
Use case: I have a “Test Company Initiative” parent initiative (company level) with child initiatives. Features are linked to those child initiatives. However, there may be one-off features that ALSO need to tie to the parent initiative because th...
Guest
almost 2 years ago
in Reports
0
Future consideration
Assignee of feature in Aha! should propagate to Gitlab
As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
Guest
about 7 years ago
in Integrations
0
Future consideration
Remember last folder used when attaching/linking a item and add favorites
I use nested folders to organize the images that I am uploading to be included in feature and item descriptions. Sometimes these folders can be very deep, six or more levels. Every time I place an image in the feature/requirement I am click the im...
Guest
about 7 years ago
in Features
0
Will not implement
Handling Use Case of Initiatives with and Without Children
Use Case: I have initiatives at the company level. I also have initiative at the product line level that roll up to the company level initiatives. Not all company initiatives have "child" initiatives. There are multiple types of reports that displ...
Guest
almost 2 years ago
in Reports
0
Future consideration
The Prefix for all Master Features is 'E', this is a suggestion to change this globally to M to align with the default terminology.
EG PRODUCT-E-123 should be PRODUCT-M-123 instead.
Guest
over 5 years ago
in Epic
1
Future consideration
When a user clicks on a URL to a saved Feature List/Idea List view, send user to that view in the workspace it was created in
We have numerous workflows that utilize 'Feature List' views and 'Idea List' views that were created for a particular workspace. When providing that URL to a user to either list view, the URL brings you to the view, but in the last workspace you v...
Ankar S
over 3 years ago
in Reports
0
Future consideration
Hi,
Unsure why this doesn't already exist, but we should be able to list followers who aren't in Aha. For example, if using Salesforce, HubSpot, etc., it would be ideal to list contacts who should be following something (feature, etc.)
This shoul...
Guest
about 7 years ago
in Application
1
Unlikely to implement