Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox
almost 4 years ago
in Jira
0
Future consideration
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Asana best practices recommend projects represent distinct bodies of work with start and end dates. The Aha! integration requires, in the set up, selection of an Asana Project to connect the workspace to. This requires a new integration for every ...
Bonnie Trei
almost 3 years ago
in Asana
0
Future consideration
Clubhouse is gaining a full head of steam and being adopted widely as a replacement for Trello and Jira - it strikes a great balance between the two. We're currently evaluating a move from PivotalTracker to Clubhouse, and while we're excited by th...
Guest
over 7 years ago
in Wanted
9
Will not implement
Add notification in Slack for Idea Created without having to specify category
What is the challenge? Currently the Slack integration doesn't have a notification type for just Created. It has a notification for Created by category and the user can technically use that and select Anything to get notifications for all ideas cr...
Peter Whisenant
5 months ago
in Slack
0
Future consideration
Map VSTS/TFS picklist custom fields to Aha! choice list fields
VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
View in Aha! the author of a comment created in Azure DevOps
In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest
over 3 years ago
in Integrations
1
Future consideration
Add Salesforce integration to Salesforce custom objects.
We use custom objects in our Salesforce org to track things like feature requests, bugs and other system support related issues. Allowing us to integrate Aha to a custom object would allow us to use the Aha integration with our existing org struct...
Guest
almost 10 years ago
in Salesforce
3
Future consideration
When using Import Records, not retaining parent/child relationship (AzDo Integration)
Who would benefit? Aha users when setting up a new workspace What impact would it make? Improves ability to only bring in needed records How should it work? After setting up integration mappings with parent/child relationships, have import records...
Guest
11 months ago
in Integrations
1
Future consideration