ADD A NEW IDEA

My votes: Integrations

Showing 950 of 8935

Rally integration - Create and update dependency relationships between features as part of two-way integration

When a feature is sent to Rally, also create predecessor and successor links according to feature links which exist in Aha! Changes to predecessor and successor links in Rally should create or delete feature links in Aha!
Matt Case about 8 years ago in Dependencies / Rally 2 Future consideration

Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile in...
Guest over 9 years ago in Jira 9 Future consideration

Integration with Assembla

We use Assembla for issue tracking and Aha! for Roadmapping. Ideally the two products would be linked to tie roadmap features and milestones to Assembla.
Guest over 9 years ago in Wanted 13 Unlikely to implement

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox over 3 years ago in Jira 0 Future consideration

Gitlab - Connect Master Features to Epics, and more

As one more request to improve connection between Aha and Gitlab :) We need better integration between Master Feature, Features and Requirements of Aha to Epics and Issues of Gitlab. A sample could be Master Features -> Epics and Features/Requi...
Fabio Brito about 4 years ago in Integrations 3 Future consideration

Map JIRA Fix Version to Aha Release Phase

We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key t...
David Vins almost 6 years ago in Jira 8 Future consideration

When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.

The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin almost 6 years ago in Jira 5 Future consideration

Integrate with Mural

Mural is a great visual management tool. Ideally Mural could be the foundation for the notes section in Aha!. Ideally....you could work on a Mural from within Aha!...so perhaps an integration of some sort. This allows for a virtual room where team...
Guest almost 7 years ago in Integrations 2 Unlikely to implement

Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with

We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi over 8 years ago in Jira 11 Already exists

Slack Channels for Features

It would be very helpful to have Slack Channels per Feature. At this moment all changes in features comes to the same channel, mixing information from different features that affect different groups. Therefore, having the ability to create an inte...
Pablo Antolín almost 9 years ago in Slack 6 Likely to implement