We typically reference feature requests by the Aha feature ID, e.g. WEB-32 or WEB-44. When we push those feature requests down to Github for development, we generally create a branch for each issue, but since we lose this information it's difficul...
David Bean
about 8 years ago
in GitHub
2
Unlikely to implement
See inherited personas in the product's Strategy/Persona's page
It's great that we can inherit personas from parent products but we need to be able to see those inherited personas in the Strategy/Persona Page of a child product ... right now you need to change PRODUCT in order to see the inherited personas whi...
Michel Besner
about 8 years ago
in Strategy
1
Unlikely to implement
The paid seat group reflects our business units and so we need to store the business unit identifier and be able to report on it. The description field could be used or preferably a custom field which provides more flexibility
Chris Brooks
about 4 years ago
in Application
0
Future consideration
Allow to lock items when date is synched with integration
Currently when Epics, Features and Requirements use a Date Sync with our DevOps it would make sense to be able to lock the dates in UI and Bar-Lenght handles as they are exclusively coming from the external system. This would avoid: A contributor ...
Michael Scholze
about 4 years ago
in User story map
0
Future consideration
Allow DevOps URL in Integration to be different for connected workitem links
Our DevOps AHA integration is using a dedicated subdomain that only allows the AHA Server IP in for obvious security reasons. Now when users click integration links within AHA's User Stories the link will not resolve as their IP gets blocked. It w...
We're using the Salesforce integration for collecting requests from our customers and we'd like to create a report in Aha! that counts the number of new requests per idea for a given time period (e.g. last 2 weeks). There's a field called "Request...
Gergo Navratyil
about 8 years ago
in Salesforce
0
Already exists
Keep unsupported 3rd party Jira tag as it is upon syncing
In Jira, it is possible to render Gherkin by using 3rd party plugin.
After modify the description field in Aha! and synced with Jira, the format is ruined by Aha!.
Original Description on Jira:{code:gherkin} Scenario: The empty state text shows...
Guest
about 8 years ago
in Jira
0
Will not implement
There needs to be an easier way to add master features in the story map without having to scroll all the way to the right, add a new one, then drag it over to the left. Perhaps just some blank space to the right of the farthest right master featur...
Gary David
about 4 years ago
in User story map
1
Already exists
This is for the Features Roadmap view. Display a thumbnail image for each feature in the release card. This would provide visual reference when sharing the roadmap view. If a feature has an inline image, include it in the Release card along with t...
Guest
about 8 years ago
in Features
1
Unlikely to implement
Ability to add a label to the blank results in a Graph or Chart
When creating a graph or a chart where there are empty or blank results. Aha! gives that result a colour with no name. Instead , allow the user to add a label, or by default it label it as blank.
Andrew Brooks
about 4 years ago
in Presentations
0
Future consideration