Link existing GitHub issues with a new Aha! Feature
The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
Turn off creating/adding a milestone in Github when pushing an Aha feature to a Github issue
My dev team currently uses Zenhub (Github integration) to organize their issues so they add a milestone corresponding to the current sprint to issues. When I push issues to Github, it automatically creates a milestone from the release name and add...
Both Aha! and Github Issues have the capability to assign items to an owner - but there is no synchronization between Aha! and Github Issues.
Ideally - within the GitHub integrations section - you could assign a Github name to every user - so when...
Sync Aha Release and GitHub Milestones whenever one is updated
Currently the Aha Release is associated to the GitHub Milestone when the issue is initially created.
Thereafter if the release or milestone are changed, the change is not reflected.
Release and Milestone should be kept in synch at all times.
It would be great to have the Github issue get a link back to the Aha feature. Quite often our developers need to reference documentation added to the Aha feature, but they don't have a good way of navigating from the Github issue back to the cor...
Please stop deleting GitHub Labels when Aha updates are pushed
We use labels to categorize and organize our work in GitHub.
When you use the "Update GitHub Issue" feature in Aha, it overwrites everything, including labels that were added in GitHub.
This is terrible because it removes all of our vital cate...
almost 3 years ago
Currently the integration between Aha! and GitHub issues is uni-directional, Aha->GitHub. So if someone changes the initial post content in an integrated GitHub issue, the next time an update arrives from Aha! that change will be blown away.
over 4 years ago
Would be great to be able to map Aha! status to GitHub labels. We use labels in Git to mark phase of the issue, because there are only 2 statuses in Git (Open, Close). This way we have more clear overview on the progress, and it would be great if ...