Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
Allow additional Link Types in the 'Links to' field
Within AHA we are mapping
Releases -> ADO Release Work Item
Master Feature -> ADO Epics
Features -> ADO Features.
Master Features need to be located in the Release in which they complete. But Features (that contribute to this M...
New features created via an ADO integration are assigned to the parent epic release by default
Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
Guest
about 9 years ago
in Integrations
11
Already exists
Mural is a great visual management tool. Ideally Mural could be the foundation for the notes section in Aha!. Ideally....you could work on a Mural from within Aha!...so perhaps an integration of some sort. This allows for a virtual room where team...
When, for example, an idea is created within aha! and the integration alerts a slack channel of this entry, it would be good to be able to customise the output of that notification and remove unwanted fields.
Guest
over 3 years ago
in Slack
2
Likely to implement
Import Name, Status and Date of release associated with Feature / Idea in Salesforce Integration
Currently, users of the Salesforce <> Aha! integration can create / link 'Aha! Ideas' to 'Salesforce Opportunities'. Further those 'Aha! ideas' can be promoted to / linked with 'Aha! Features'.
As a user of the Salesforce <> Aha! int...
Erick Crowell
over 7 years ago
in Salesforce
1
Future consideration
The names of the people we do business with is very important. The Salesforce integration should sync the contact names of our clients in Salesforce with the Ideas portal to enure consistancy and data consistancy.
Daniel Lynch
over 2 years ago
in Salesforce
0
Future consideration
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S
over 2 years ago
in Jira
0
Future consideration
Allow Aha! user name to populate DevOps board user
When working with multiple users, we need to be able who created what, commented on or changed something. As of right now, the user name (Admin) of who configured the Integration (Azure DevOps Services) is the one that appears on every item in Dev...