ADD A NEW IDEA

Integrations

Showing 105

Link Features to Multiple JIRA Projects

This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...
Ryan Schultz over 8 years ago in Jira 0 Already exists

Integrate with Freshdesk

Integrate with fresh desk for ideas and bugs
David Cordner over 8 years ago in Wanted 8 Already exists

enhanced Kanban workflow - Similar to leankit or swiftkanban

we are in the process of switching over to Swiftkanban as the kanban board is great to use and allows us to create end to end workflow. We will more than likely continue to use AHA for strategy but ideally we are looking for a single solution tha...
Guest over 8 years ago in Wanted 2 Already exists

Allow users to refresh all Aha! features from a linked JIRA integration.

Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow over 8 years ago in Jira 0 Already exists

JIRA integration - Send to JIRA - labelling

Hi Guys We have mutiple JIRA to single Aha! product, so when sending we see the image attached. You cannot distinguish which JIRA in this list - please extend to: Send to JIRA: VIS - where VIS is the name of the JIRA project. Seems a simple qu...
Andrew Tipton over 8 years ago in Jira 2 Already exists

Pull JIRA Original Estimate not Remaining Estimate

We use sub-tasks or even regular tickets in JIRA to do our estimates so they can be planned into sprints. When these estimate tickets are closed on the JIRA side it seems that the estimates they are for are zeroed out on the Aha side. The only thi...
Guest over 8 years ago in Jira 0 Already exists

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 over 8 years ago in Jira 0 Already exists

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 over 8 years ago in Integrations 6 Already exists

Work with Confluence for PRD Documents

Currently we use Confluence PRD documents: https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint It would be great if we could find some way to combine this with Aha. Otherwise, we spend time duplicating information from insi...
Guest almost 9 years ago in Integrations 11 Already exists

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 almost 9 years ago in Jira 0 Already exists