All ideas
Sort by:
Trending
Status:
Showing 8936
10
VOTE
Allow votes to be automatically returned to voter when an idea is Declined
My understanding is that your Ideas platform currently doesn't support automatically returning votes for any status beyond 'Done' and 'Shipped'. Our users have requested that votes be returned for declined ideas, which I think makes a lot of sense...
1
Future consideration
9
VOTE
Reference Fields for Capacity Estimates Costs, Teams & Team Hours
We'd like to be able to pull information from the capacity planner fields: team name, team hours & cost per team. There is already some kind of way to do this within the pivot table that comes with the capacity planner; however, we'd like to s...
0
Future consideration
1
VOTE
Ability to Integrate Ideas with Jira Service Desk
What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
0
Future consideration
1
VOTE
Use AI to build segments for organizations
What is the challenge? Understanding ideas based on organization segments. What is the impact? Using AI to build segments could potentially surface connections between organization attributes. Allowing for better understanding of different market ...
0
Future consideration
1
VOTE
Ability to list users who are using API Keys
What is the challenge? Users have generated API Keys to update Aha and the Account Admins would like to know which users are using API Keys. What is the impact? How can we know who is updating using an API and understanding where the API is used t...
0
Future consideration
2
VOTE
Displaying requirements within the Retrospective report
Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...
0
Future consideration
3
VOTE
Account Admins have the ability to configure the account level Integration record mappings
Issue? The default Rally integration record mappings are Feature / Release / Requirement. Every new integration is being given the three record default which is confusing Aha users and enables users to deviate from the best practice of feature to ...
0
Future consideration
3
VOTE
Allow multiple Aha! accounts to integrate with the same Salesforce instance
In my organization we have separate Aha! accounts for each business unit. We use one Salesforce instance across our organization. I would like to be able to integrate our multiple Aha! accounts with our Salesforce instance.
0
Future consideration
6
VOTE
Redirect users to accessible version of link if they do not have access to internal link
Users submit requests via an externally facing portal. Once that request is received, the team handling the request have one view of the request, while those who do not have that internal access can only see the publicly visible version of the req...
0
Future consideration
15
VOTE
Derive the Master Feature Release(s) based on Child Features
It'd be great if I had an option to have the system derive the release(s) that a Master Feature belongs to based on the release(s) that the Features that tie up to the Master Feature are slotted in. This would include the ability for the master fe...
4
Future consideration