Integrations
Sort by:
Trending
Status:
Showing 945
6
VOTE
Ability to configure integrations not to create new records in Aha
In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA.
I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
0
Future consideration
2
VOTE
Add Boolean Field mapping for Rally 2.0 Integration
Currently, there is no way to map Boolean fields in Rally to Predefined Choice fields in Aha. A Boolean field in Rally can only be mapped to a text field or a few other options like Aha Rank, and can only bring the data from Rally to Aha, not the ...
0
Future consideration
1
VOTE
Add option to show additional columns/fields in "Integration updates" window for Jira
The "Integration updates" window currently only shows the issue summary of incoming issues. Presumably the JSON payload being received by Aha contains the full set of information for the incoming issue ... it would be incredibly valuable to be abl...
0
Future consideration
3
VOTE
Integration between Aha! and Jira Align (formerly Agilecraft)
Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
1
Future consideration
3
VOTE
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
0
Future consideration
2
VOTE
Calculated mapping of number fields in integration with Jira
We would like to specify a conversion factor or formula to map numeric fields between Jira and Aha! numeric fields, especially a Jira number field and Aha!'s Original Estimate field. This would allow us to enter hours into a Jira number field whic...
0
Future consideration
8
VOTE
better redmine integration - requirements are children of features, and tasks are children of requirements
redmine integration is very helpful and needed.
"When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue."
there should be a way of re...
0
Unlikely to implement
8
VOTE
Show JIRA # rather than Aha # on Roadmaps
JIRA came first at our company, and only a handful of users use Aha -- consequently, when I publish a roadmap, it is assumed that the issue numbers shown on the roadmap are JIRA issue numbers -- this creates a lot of confusion. I would like to be ...
2
Unlikely to implement
8
VOTE
Integrate Gliffy to enable editable flow diagrams in notes
I currently have to create flow diagrams outside of Aha and paste in a static version that others can not change. This is very restrictive and does not follow the collaborative flow I like to use.
https://www.gliffy.com/
3
Unlikely to implement
4
VOTE
Azure DevOps integration support for designating default Iteration as backlog
Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
2
Future consideration