When promoting an idea to a feature I would like to be able to define the "Epic" instead of the release that I want it related to. Not having this ability creates "orphaned" features that don't have an epic and I have to then find them again and a...
Guest
almost 4 years ago
in Ideas
0
Future consideration
The ability to create mockups within Aha! to illustrate simple flows or concepts it great. However, it can be difficult for reviewers to read some of the information displayed in the mockup in "review" mode because the image gets fitted within the...
JP Guyon
almost 6 years ago
in Mockups
0
Will not implement
Provide a public API (as part of the Aha! REST API) which can be authenticated against using an Ideas Portal SSO token (JWT) the same way as we do authentication for the web version of Ideas Portal. This means the API's logged in user would be an ...
Adam Burley
almost 4 years ago
in Integrations
0
Future consideration
Ability to map releases in the same product area to multiple workspaces in Rally
We have times when releases need to be under a particular product in Aha!, yet when they get pushed to Rally, they belong to more than one Rally board. It would be extremely helpful to pick which board in Aha! we are sending the release to in Rall...
Guest
almost 6 years ago
in Rally
0
Already exists
Allow customization/formatting in the feature or initiative detail record
It would improve the user experience if in the feature/initiative record we could: 1) have the ability to hide from view components that are not being used (such as features and releases), otherwise the detail record can be very long and "messy" f...
Guest
almost 6 years ago
in Account settings
0
Unlikely to implement
Ability to push updates to integration that has come from another integration
Long story short.
Our company uses Jira for Customer Service ticketing system and Development team uses Azure DevOps. In between we have Aha! where all features and roadmap is managed. When we take bug fix or improvement task from Customer Service...
Mikko Kylmälä
almost 6 years ago
in Integrations
0
Future consideration
Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited
In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
Kevin Burges
almost 8 years ago
in Jira
0
Unlikely to implement
Apply filters to the Milestone Chart View and keep milestones off the chart until explicitly charted
We have a long list of master features for our product line that need to be prioritized at that level. It would be helpful to do it iteratively, and one way to do that is with filters that allow us to focus just on the master features associated w...
Guest
almost 6 years ago
in Epics
0
Unlikely to implement