Enhance aha to github integration to include Projects Beta
We started looking into testing the integration with github.com and aha and noticed that Github has new functionality ‘Projects Beta’ which gives users spreadsheet like functionality to group issues and pull requests (screenshots attached). These ...
Right now you can only define default values for TFS fields. It would be better if there was a way to map fields in AHA to fields in TFS, including custom fields. This could be done by using variables (aka: {{Assignee}}) in the current UI or provi...
Add support for linking to multiple different JIRA issue types
We would like to roadmap product releases with new up-coming features and bug fixes. Aha features currently map to Jira stories but we'd like to map to Jira 'Bug' and possibly 'Improvement' types as well.
Integration with TFS 2015 on prem which includes the Rest API: https://www.visualstudio.com/en-us/news/tfs2015-vs.aspx#restapi This is the first release that brings REST APIs to on-premises TFS.
Re-enable conversion of Features to Requirements when JIRA integration is active
In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously...
Integrations 2.0: List view bulk edit Send to for integrations 2.0
Integration 1.0 integrations have the List view option for bulk editing Send to ----.
The integrations available to send to do not include 2.0 integrations.
2.0 integrations should be supported for bulk sending operations just like 1.0 integrations.
Danny Archer
about 7 years ago
in Integrations
6
Shipped
Map feature "Value" field in Salesforce integration to a custom field instead of the opportunity value
We need a tool that helps us quantify the potential value/ROI of a feature (to the extent that this is possible...). The SF/Aha! Integration ties to the standard opportunity amount field in SF, but that field is not the metric that we care about i...
For Project Status, currently the only information we have is feature and requirement status coming from Aha to VSO / VSTS and vice versa. It would be far better for businesses tracking effort to be able to put estimates into either tool synchroni...
Support for "Select list (cascading)" field type in JIRA
JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...