What is the challenge? Rally Project name is updated but the project name is not updating in the Aha Integration Project Tab? What is the impact? Users see the wrong project name in the Aha integration and think they need to create a new integrati...

Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.

The AHA window size in the visualforce pages is so small and users have to scroll to view the entire list of ideas related to an Account/Case/Opportunity. It would be great if we can customize the AHA layout in Salesforce(adjust the height of the ...

When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA proj...

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...

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering

It is almost solves the whole bunch of tasks about integration with google drive and docs in an easy, useful and competitive manner.

There are a few instances when it would be valuable to report on the name of the integration that an object is using to connect with an external development system. This would help to identify when integrations are being 'cut over' in order to tra...

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.