ADD A NEW IDEA

Integrations

Showing 637

Allow link of a requirement to a release (sprint)

We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
Guest about 1 year ago in Azure DevOps Services and Server 0 Future consideration

Ability to set add-only templates to integrations

We currently use integration templates as a way to enforce standards across our organization. We would like the ability to for others to use the template, but only in an additive manner. We would like others in the organization to use our template...
Ron Yang almost 5 years ago in Integrations 2 Future consideration

Import functionality to show the entire list of records and have ability to import only selected (check box) records

Currently Rally import functionality shows only top 10 records extracted for the set criteria. Want the ability to see all the records with checkbox to allow 'pick & choose' for import Do not show the records which were already imported or linked
Jyothirmayi Talaparthy over 3 years ago in Rally 3 Future consideration

Add ability to transfer requirements between features and features between master features (epics)

If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's). However we are...
Richard Harrison about 6 years ago in Azure DevOps Services and Server 0 Future consideration

Integration with Aha!

If one of my business partners used Aha! -- I'm trying to sell them on it -- it would be really cool, in theory, to be able to integrate with their instance. They currently use Pivotal Tracker and I integrate some features with them. If they moved...
Tom Beck about 5 years ago in Wanted 0 Future consideration

Add filters to integrations to prevent sending records that meet criteria

It would be useful to be able to create filters to prevent certain records from being sent to Azure, JIRA, or other integrations. For many workflows, there may be "raw" working records in a release backlog that are not ready to go to engineering t...
Ronnie Merkel almost 4 years ago in Integrations 2 Future consideration

Synchronize Organization with Azure DevOps

We are storing a client name on user stories and bugs in ADO and it would be great to be able to be able to sync this field between ADO and Aha! using the organization field that has now been made available to all Aha! objects (and not only ideas)...
Nicolas Andrillon over 2 years ago in Integrations 0 Future consideration

Integrations 2.0 List field mapping is hard with long lists

Issue with list field mapping with integrations 2.0 when your list of available values is long. If you have a custom list field with lots of values (20+) and a corresponding long list field in Jira. To map the values between the two systems is ver...
Tom Bailey over 6 years ago in Integrations 1 Future consideration

Synchronise mockups to other integrations

Currently, when a mockup is updated or deleted, the file does not stay in sync with an integrated system. Ideally, the same mockup file would continue to get updated across the systems.
Toray Altas over 6 years ago in Application / Integrations / Mockups 1 Future consideration

Import of time tracker data from 7pace Timetracker to Aha!

7pace timetracker is an integrated time mamagement solution for teams using DevOps. We would like to pull time tracker data into Aha! through our DevOps integration to ensure Aha! has a clear view of the time spent on Features.
Guest almost 4 years ago in Azure DevOps Services and Server 0 Future consideration