When we create a feature in Aha! and then send it to Trello, we need some way to query for all cards associated with a given release. Currently there's no easy way without retagging all the cards or manually populating a custom Trello field
We want to use labels in Aha to indicate major clients associated with a given feature. When we sync. to Trello, we need that information on our Trello cards.
Features created due to integration to appear on Releases - Overview, Details view
This would be very helpful since without it Product Manager doesn't get to know if Dev team has added any new stories during grooming. Currently such stories although result in creating features, they are only visible on Feature Board view under r...
The SFDC integration is fantastic, but we're finding the association with an Opportunity or Case aren't really the right place for us to make a relationship with Ideas. Most of our customer feature requests arrive after the opportunity has closed,...
Aha should be focused on managing the full lifecycle of the agile process. Today you can only link a feature to an epic when I really need to link an initiative to an epic. I would like the Rally integration to be like the Like the JIRA integratio...
It's already possible to send notifications from Aha! to Slack, but the messages are pretty messy and they don't always contain the information that I need. I want the ability to better customize the messages posted in Slack, particularly: What tr...
Nathaniel Collum
about 2 years ago
in Slack
0
Shipped
Adding a new Feature and Requirement Type option in the Rally Configuration screen
We like being able to capture Requirements in Aha but we have occasions when we don't want them to go to Rally as User Stories, Features or Initiatives. Therefore, we would like to add a 5th option on the Feature and Requirement Type select box to...
Add configuration to JIRA integration so that version creation is optional
Some users may not want versions created in JIRA for each release in Aha! Add an option to the JIRA integration configuration to disable the creation and linking of releases to versions.
Mapping of Initiatives to other ticket types in Jira
Currently Aha! allows only mapping of initiatives to Jira Epics. Now that Jira enables unlimited hierarchy, custom defined by portfolio managers, it would be nice to be able to load ticket types from Jira and map Aha! initiatives to ticket types o...