Integrations
Sort by:
Popular
Status:
Already exists
Showing 105
3
VOTE
Allow Relating Multiple Github repositories to a Single Product
This is how things works in reality for complex applications.
We have a very modular architecture for a product. ( micro services ). One product can have up 10 repositories. Even the simplest application would have frontend and backend repositori...
4
Already exists
3
VOTE
Support Personal Access Tokens vs Alternate Credentials
Visual Studio Team Services is encouraging people to move to PATs from Custom Credentials in the integrations. They will probably deprecate it in the not-so-distant future, and it's a reasonable move in general as they're more secure and easier to...
0
Already exists
3
VOTE
Link Features to Multiple JIRA Projects
This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...
0
Already exists
3
VOTE
enhanced Kanban workflow - Similar to leankit or swiftkanban
we are in the process of switching over to Swiftkanban as the kanban board is great to use and allows us to create end to end workflow.
We will more than likely continue to use AHA for strategy but ideally we are looking for a single solution tha...
2
Already exists
3
VOTE
Pivotal Tracker: 2 way sync for Requirements — not just Features
Today PT can only update status in Aha for Features. We'd like to have it update the status of requirements as well.
In our case, it's particularly useful because we map Aha Features to PT Epics (and Aha Requirements to PT Stories). So we're bli...
2
Already exists
2
VOTE
Add more filters to integrations import
Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
0
Already exists
2
VOTE
Ability to use "belongs to" relationship in Aha to map to "is contained by" link type in Jira
I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...
1
Already exists
2
VOTE
Allow integration with custom work item types
Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...
3
Already exists
2
VOTE
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship.
Enable the parent - child hierarchy for Aha tool so that we can see the view for parent-child relationship. Same like Jira we have parent -child relationship concept of subtask we need in Aha same functionality.
3
Already exists
2
VOTE
