Better presentation of text when integrating to an existing field in ADO
Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...
Integrations 2.0: Allow Master Feature relationship for Requirements
I can create a relationship for Releases at the requirement level even though requirements do not inherently have a release field, this appears to be derived from the feature. I should also be able to create a relationship to the Master Feature in...
Danny Archer
almost 7 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...
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ä
about 5 years ago
in Integrations
0
Future consideration
Allow fields from linked records to be mapped to integration fields
It would be useful to be able to map additional data from linked records when setting up integrations with my development system.
For example, when configuring the feature field mapping I may want to pass over the initiative a feature is linked to...
Todd Meyer
about 7 years ago
in Integrations
0
Will not implement
We need to link Aha! Roadmap items to other items in Sparx EA (OSLC compliant) using ArchiMate 3.1 and an OSLC connector for Aha! will enable us to do that. This connector will also enable us to link Sparx EA ArchiMate 3.1 model elements such as s...
Guest
over 3 years ago
in Wanted
0
Future consideration
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
Daniel Pokrývka
over 5 years ago
in Jira
2
Future consideration
ability to integrate idea information into Azure DevOps
We use the ideas portal to solicit new enhancements from our users and then link those ideas to features in our products. The problem is only our product management and dev management use Aha. our development team uses Microsoft DevOps to track th...