Map user profile pictures from Salesforce community to Aha Ideas portal!
We want a seamless experience for our customers that are logged into our Salesforce community. Users have the ability to set their avatars in the Salesforce community but when they flow into the Aha ideas portal their avatar is not transferred ove...
Andrew C
over 9 years ago
in Salesforce
0
Unlikely to implement
Allow VSO integrations to work with multiple Aha Products represented in a single VSO Project
Some customers have specified that they maintain a single VSO Project, but represent a number of products beneath it. The way to handle that now in Aha is to set up a web-hook for each product in Aha, and then create a subscription in VSO that fil...
Allow users to refresh all Aha! features from a linked JIRA integration.
Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow
over 9 years ago
in Jira
0
Already exists
Hi Guys
We have mutiple JIRA to single Aha! product, so when sending we see the image attached. You cannot distinguish which JIRA in this list - please extend to: Send to JIRA: VIS - where VIS is the name of the JIRA project. Seems a simple quic...
Andrew Tipton
over 9 years ago
in Jira
2
Already exists
Allow tracking simultaneous tracking of both Feature-Level and By-Requirement estimates
The current AHA/JIRA estimate integration allows feature level OR requirement level estimates, however as we don't use JIRA for time tracking we want to use JIRAs 'Original Estimate' field with AHA's per-requirement estimates.
My suggestion would ...
Guest
over 9 years ago
in Jira
0
Unlikely to implement
Pull JIRA Original Estimate not Remaining Estimate
We use sub-tasks or even regular tickets in JIRA to do our estimates so they can be planned into sprints. When these estimate tickets are closed on the JIRA side it seems that the estimates they are for are zeroed out on the Aha side. The only thi...
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
over 9 years ago
in Jira
17
Future consideration
Assignee does not get sent to Jira if using Default Assignee functionality
If you use the "default assignee" functionality, then that assignee will not get sent to Jira, even if that user exists in Jira. This could be considered a bug.
Avigail Ehrenhaus
over 9 years ago
in Jira
0
Already exists
Better error handling when Trello card to move across boards
It is common practice for teams to have multiple Trello Boards. For example, in our organization, we have our "current development" board with Next Up, In Progress, Awaiting Validation, Completed ... and but like any product organization, you do n...
Angus Davis
over 9 years ago
in Trello
0
Will not implement
Set the TFS Iteration and Area path per feature or requirement
Having a single area path for the entire product doesn't make sense. This value will usually depend on the feature, as area paths define the area of code impacted by a work item. This helps with evaluating code churn and test coverage. It needs to...
Jonathon Leeke
over 9 years ago
in Integrations
6
Already exists