My ideas: Integrations
Sort by:
Popular
Status:
Shipped
Showing 943
18
VOTE
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...
3
Future consideration
18
VOTE
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...
9
Future consideration
18
VOTE
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.
5
Future consideration
18
VOTE
18
VOTE
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.
11
Already exists
18
VOTE
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...
6
Likely to implement
18
VOTE
Convert story to epic in Jira when promoting requirement to feature
In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
2
Unlikely to implement
18
VOTE
17
VOTE
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
2
Future consideration
17
VOTE
View in Aha! the author of a comment created in Azure DevOps
In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
1
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved