Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 922

Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release

Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
Josh Tambor over 4 years ago in Jira 0 Future consideration

Allow integration with Rally calculated fields

It is not currently possible to map to Rally calculated fields in the integration with Aha! Roadmaps, but it would be useful to be able to do so (for example, to map to a field that calculates).
Russell Glenn about 2 years ago in Rally 0 Future consideration

Better Slack Integration with Fixed Workflow Approvals

User Story: As a product manager for one piece of the product, I want to post an alert in a specific Slack channel when a fixed workflow/approval "to-do" is created, so that those who have disabled email notifications or browser alerts are aware t...
Guest over 4 years ago in Slack 0 Future consideration

Integration of leankit kanban

Need a reference link to the card (like in Trello=
Guest almost 9 years ago in Integrations 0 Unlikely to implement

Adaptive Integration

Need to integrate our resource management ‘Adaptive’ tool to our portfolio planning ‘Aha’ tool. Teams are putting lot of manual hours to align our data in Adaptive to initiatives in Aha. Integration will help reduce waste and be leaner on this pro...
Guest over 6 years ago in Integrations 0 Unlikely to implement

Features should Inherit initiatives from Release & Master Release so all Pivotal stories are under the Epic after sending to PT (and the Epic is actually created)

When pushing a feature to Pivotal Tracker, a user can select a mapping that allows for initiatives to be mapped to epics. The only initiatives this works for are initiatives directly referenced by a Feature. Any initiatives referenced by the Relea...
Guest almost 9 years ago in Pivotal Tracker 7 Unlikely to implement

The Aha <->Jira Integration Mappings should be Transparent to User

Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Guest about 2 years ago in Jira 1 Already exists

API access for links, generally

A previous idea of mine requests access for when Master Features are mapped as dependencies against Features, or vice versa. That one is a showstopper for my firm. However, it turns out that linking, say, an Idea against a Feature is also inaccess...
Frank Siler over 4 years ago in Wanted 0 Future consideration

JIRA integration without admin account rights

At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
Guest about 9 years ago in Jira 0 Already exists

Do not Require first filtering by Product in the "Request an Idea" Salesforce Visualforce Page

Having to first filter by Product (and not having an "all Products" option when searching for an existing Idea in the Request an Idea visualforce page) means that a user may miss an existing idea because they are not in the right Product. We shoul...
Guest over 4 years ago in Salesforce 0 Future consideration