Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Integrations

Showing 813 of 7458

Assignee does not get sent to Jira if using Default Assignee functionality

If you use the "default assignee" functionality, then that assignee will not get sent to Jira, even if that user exists in Jira. This could be considered a bug.
Avigail Ehrenhaus about 7 years ago in Jira 0 Already exists

Better error handling when Trello card to move across boards

It is common practice for teams to have multiple Trello Boards. For example, in our organization, we have our "current development" board with Next Up, In Progress, Awaiting Validation, Completed ... and but like any product organization, you do n...
Angus Davis about 7 years ago in Trello 0 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 7 years ago in Integrations 6 Already exists

Delete trello card associations less aggressively

When a user is working on a feature in Aha that is linked to a Trello card, if she accidentally changes the release for this feature to the release of a different product (e.g. the Demo Fredwin cycling product), the trello linkage is immediately d...
Angus Davis about 7 years ago in Trello 0 Unlikely to implement
118 VOTE

ServiceNow integration

Ability to create and manage ServiceNow epics through Aha! Product Management would define the epics and they would flow down into ServiceNow
Guest about 7 years ago in Integrations 27 Future consideration

Integration with Collabnet

http://www.collab.net/products/teamforge Our development team uses Collabnet and as much as I would like to convince them to use Jira I do not think that is a realistic possibility, so this is a request for Aha to integrate with Collabnet.
Guest about 7 years ago in Wanted 0 Future consideration

Salesforce integration without permission set

Currently, the Salesforce / Aha.io integration requires using a permission set. A System Administrator must assign individual users in Salesforce to this permission set, in order for them to use the Aha.io ideas portal. That's a fine approach, but...
Angus Davis about 7 years ago in Salesforce 1 Future consideration

Two-way integration with Redmine

Two-way integration with Redmine.
Chris Waters about 7 years ago in Integrations 9 Future consideration

Setup integrations on Product Lines

It would be very nice to setup our pivotal tracker integration on a product line. That way if a ticket moves between products in that product line it retains the integration that was configured for it.
Jason Novek about 7 years ago in Pivotal Tracker 3 Unlikely to implement

When I move a feature to the parking lot in Aha, it should move to the icebox if it exists in Pivotal

Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint. When this happens,...
Jason Novek about 7 years ago in Pivotal Tracker 0 Future consideration