Share your product feedback

ADD A NEW IDEA

Integrations

Showing 944

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 9 months ago in Azure DevOps Services and Server 0 Future consideration

Include Attachment for Release In Integration

What is the challenge? For Releases Attachments are not supported in Integration Set Up How would you solve it? Manually Project Managers are uploading in Devops What impact would it make? It will reduce so much of manual work
Guest 9 months ago in Azure DevOps Services and Server 0 Future consideration

Allow mapping fields from related records in Aha to Azure Devops

This idea is to allow mapping fields from related records from Aha to DevOps. In most cases, this would be parent/grandparent/great grandparent situations. For example, allowing a tag from an Aha feature to be mapped to a tag on a DevOps PBI. Anot...
Josh Wayne about 3 years ago in Azure DevOps Services and Server 0 Future consideration

Persistent filters for integrations and incoming product updates

Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest about 6 years ago in Jira 0 Future consideration

Integration of feature flags of ConfigCat

Would be great if we could send the statuses of the ConfigCat feature flags back to Aha, to monitor released features.
Kristof Dewulf almost 4 years ago in Wanted 2 Future consideration

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

Automated access to a workspace when user selects given workspace

This is the proposed Use Case scenario: If a user receives contributor(Product Manager) access in a named workspace Then automatically grant access read access to integration templates Jira/Rally/Github)
Karla Johnson over 1 year ago in Integrations 0 Future consideration

Pivotal Tracker Integration Mapping

It would be helpful if one of the mapping options with Pivotal Tracker could include the following options: Master Feature to Epic Feature to Story Requirement to Task Instead, the only option for mapping to Epics in PT is to use Initiatives. Th...
Tom Beck about 6 years ago in Pivotal Tracker 1 Future consideration

Show comments added in JIRA as part of a state transition.

Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA. This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi over 5 years ago in Jira 2 Future consideration

Change default visibility of ideas submitted via Slack

I recently installed the Slack integration. When one of our team members submits an idea via Slack, it shows up in our Aha dashboard but not on the associated portal page. As of right now, I believe I'd have to change the visibility of each new id...
Guest about 6 years ago in Ideas / Slack 0 Future consideration
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved