My votes: Integrations
Sort by:
Trending
Filter by:
Status
Showing 947 of 9056
19
VOTE
Rally integration - Create and update dependency relationships between features as part of two-way integration
When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!
2
Future consideration
5
VOTE
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...
0
Future consideration
22
VOTE
Have users in Jira and Aha matched for comments, updates etc
I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there.
Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the p...
1
Unlikely to implement
13
VOTE
Auto Resend all Fields per release
Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
2
Future consideration
14
VOTE
15
VOTE
Develop Aha! triggers for Microsoft flow
Microsoft flow has over 175 triggers currently available. Examples include Zendesk - When an Item is created, Wunderlist - When a New task is created, Saleforce - When a record is created, Pivotal Tracker - When a story is created, etc. Having acc...
0
Future consideration
9
VOTE
16
VOTE
13
VOTE
17
VOTE
© 2024 Aha! Labs Inc.•All rights reserved