Trello cards should contain link back to integrated Aha item
Our product team uses Aha to plan our releases at the Master Feature level. Dev team leaders then "task" these Master Features out as Features and send the Features to Trello, where additional information is added by developers (and where workflow...
Guest
about 6 years ago
in Trello
2
Unlikely to implement
Currently, the Salesforce / Aha.io integration requires using a permission set. A System Administrator must assign individual users in Salesforce to this permission set, in order for them to use the Aha.io ideas portal. That's a fine approach, but...
Angus Davis
about 10 years ago
in Salesforce
1
Unlikely to implement
Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited
In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
Kevin Burges
about 8 years ago
in Jira
0
Unlikely to implement
Ability to map releases in the same product area to multiple workspaces in Rally
We have times when releases need to be under a particular product in Aha!, yet when they get pushed to Rally, they belong to more than one Rally board. It would be extremely helpful to pick which board in Aha! we are sending the release to in Rall...
Ability to push updates to integration that has come from another integration
Long story short.
Our company uses Jira for Customer Service ticketing system and Development team uses Azure DevOps. In between we have Aha! where all features and roadmap is managed. When we take bug fix or improvement task from Customer Service...
Mikko Kylmälä
about 6 years ago
in Integrations
0
Future consideration
Provide a public API (as part of the Aha! REST API) which can be authenticated against using an Ideas Portal SSO token (JWT) the same way as we do authentication for the web version of Ideas Portal. This means the API's logged in user would be an ...
Adam Burley
about 4 years ago
in Integrations
0
Future consideration
Assignee of feature in Aha! should propagate to Gitlab
As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
Guest
over 8 years ago
in Integrations
0
Future consideration
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
Daniel Pokrývka
about 6 years ago
in Jira
2
Future consideration