Integrations

Showing 946

Expose Rally's Flow State Field in Aha Integrations

In Rally, teams often create unique workflows using the team board. The states of the team board are captured in Rally's Flow State. To match team's custom workflows in Aha the Flow State field should be exposed.

Stephen Wingert almost 4 years ago in Rally 0 Future consideration

1 VOTE

Add "Select all" option to Integration Updates page

As a user, I want the ability to "select all" updates on the Integration Updates page, so that I do not have to select each change to send manually. When the user has set up integrations on a workspace, if there are issues with some of the integra...

Harrison Hopkins almost 4 years ago in Jira 3 Already exists

1 VOTE

Allow DevOps URL in Integration to be different for connected workitem links

Our DevOps AHA integration is using a dedicated subdomain that only allows the AHA Server IP in for obvious security reasons. Now when users click integration links within AHA's User Stories the link will not resolve as their IP gets blocked. It w...

Michael Scholze almost 4 years ago in Azure DevOps Services and Server 0 Future consideration

2 VOTE

Integrate with Bugsnag

We use Bugsnag to detect and diagnose bugs & issues. It would be great to link these directly with Aha, similar to how it integrates with JIRA, GitHub, Trellor, PivotalTracker. Bugs and issues are a key part of the roadmap.

Guest about 8 years ago in Integrations 0 Unlikely to implement

2 VOTE

Microsoft Teams - (365), allow presentation of notebooks or roadmap slides

Microsoft Teams is now available and currently supports hooks for Aha for data feeds. Microsoft Teams also supports the ability to populate a Tab. Currently they have support for the VSO Kanban board, Power BI, Excel, etc. It would be great if you...

Guest about 8 years ago in Integrations 0 Already exists

2 VOTE

Would it be possible to not need a paid AHA account to process VSTS updates?

At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...

Guest about 8 years ago in Azure DevOps Services and Server 1 Unlikely to implement

1 VOTE

Add Closing Comment for Jira Integration

Our Jira environment has a requirement to enter a comment when "closing" a ticket. Aha does not have a place for this so if Aha! users close a feature in Aha, they will have to login to Jira and close it there as well. The request is to allow a "c...

Guest about 4 years ago in Jira 0 Future consideration

2 VOTE

Edit Word Document in Aha!

We attach a lot of Word Documents in Aha. It's painful for me to open, download, edit, save again on my computer, re-upload, and delete the previous version of the document.

Analisa Meyer about 8 years ago in Integrations 2 Will not implement

2 VOTE

Fetch report data via API

I would like fetch a saved report via the API that includes features, release details, various feature data, and linked initiatives without making several hundred requests. The end goal is to feed this data to internal prioritization tooling. Base...

Guest about 8 years ago in Integrations 1 Already exists

2 VOTE

Github issues to get Aha feature ID in their name

We typically reference feature requests by the Aha feature ID, e.g. WEB-32 or WEB-44. When we push those feature requests down to Github for development, we generally create a branch for each issue, but since we lose this information it's difficul...

David Bean about 8 years ago in GitHub 2 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY