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!
Matt Case
over 8 years ago
in Dependencies / Rally
2
Future consideration
What is the challenge? There's currently no way to sync feature dates in their entirety to Trello. Aha's current integration only surfaces Trello's Due date for mapping, meaning that it's impossible to do do time-based planning across platforms as...
Guest
5 months ago
in Trello
0
Future consideration
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...
What is the challenge? Often times our Engineering counters in will convert stories/Spikes/Tasks to Epics in Jira What is the impact? We're not always told when these conversions happen and often have to do duplicate work to go into Aha! and conve...
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 ...
Guest
almost 6 years ago
in Jira
2
Future consideration
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...
Currently, if an activity webhook event fails to be sent - we have no way of resending the event - regardless what error is sent. It would be ideal if: 1) There was an automatic resending of failed events after a period of time. 2) A way to manual...
Guest
over 1 year ago
in Integrations
0
Future consideration
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...
Guest
almost 7 years ago
in Integrations
0
Future consideration