Integrations

Showing 114

Rally Project name change should be reflecting in the Aha! Integration

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

Mike Jacobson 7 months ago in Rally 1 Already exists

25 VOTE

Work with Confluence for PRD Documents

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

Guest over 9 years ago in Integrations 11 Already exists

18 VOTE

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

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.

Kevin Konishi over 8 years ago in Jira 11 Already exists

14 VOTE

Allow users to modify the AHA visualforce pages in Salesforce integration

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

Guest over 5 years ago in Salesforce 1 Already exists

14 VOTE

When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog

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

Guest about 10 years ago in Jira 1 Already exists

12 VOTE

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 about 9 years ago in Integrations 6 Already exists

11 VOTE

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field

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

Guest almost 7 years ago in Jira 1 Already exists

11 VOTE

Attach a Google Drive folder link (and files also) to issue/task/story

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

Guest over 7 years ago in Integrations 1 Already exists

10 VOTE

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 about 9 years ago in Jira 0 Already exists

9 VOTE

When a feature is sent to Github that has images attached, can the images be shown inline rather than as links?

When I send a feature to Github that has images attached, the images show up in Github as links rather than inline which is how they would show up if I had created the feature in Github. It's easier and cleaner for our developers to see the images...

Guest over 7 years ago in GitHub 0 Already exists

Share your product feedback

Please enter your email address

FILTER BY CATEGORY