Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
Guest
over 1 year ago
in Jira
0
Future consideration
I'd like to build a slick integration between Hornbill and Aha!. Similar to the integrations you already have for Zendesk and Salesforce - we're looking to be able to create or update Ideas from Hornbill workflows, and to have Aha! provide Idea st...
Guest
over 6 years ago
in Wanted
1
Unlikely to implement
Gmail Sidebar Add-on for Tasks OR bi-directional task integration
Create add-on for new Gmail interface to view and minimally manage to-dos/tasks and features. I've been increasingly using google tasks as a result of it being integrated into sidebar. Or bi-directional integration to sync google tasks.
Kyle Carpenter
over 6 years ago
in Integrations
2
Future consideration
Customize slack commands terminology to align with company's Aha! terminology
Slack uses the default Aha terminology and it is unable to customize to suit user's preference. Not having this customization is very confusing to the users when updating Aha via slack. An improvement on this feature to allow customization will en...
Guest
over 6 years ago
in Slack
1
Unlikely to implement
Integration of release (project), features, requeriments & to-do list with the project system of basecamp (with the todo feedback and comments) and same things with attachments.
Guest
over 9 years ago
in Integrations
1
Unlikely to implement
Add to the integration report if the "Based on Template" flag is checked or on the mappings page
We currently have over 200 active integrations. Knowing which ones are using the "Based on Template" flag is really useful when planning changes to the integration and ensuring that mappings are kept consistent amd not becoming unmanageable.
Andrew Brooks
about 3 years ago
in Integrations
0
Future consideration
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
Daniel Hirschberg
almost 5 years ago
in Jira
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
over 3 years ago
in Integrations
0
Future consideration