Hey, GitHub projects/issues support a new field type: iterations. With these iterations you can model sprints for sprint planning. However, custom fields of this type do not show up in the field mapping list for GitHub-integration in aha.io (yes, ...
Guest
5 months ago
in GitHub
0
Future consideration
Github is adding functionality to extend how tasklists are used and increase tracking and linkages between items. The Aha integration should be capable of supporting this - particularly the linkages and tracking between related items https://docs....
Guest
5 months ago
in GitHub
0
Future consideration
In GitHub integration, we would like to map a custom field called "Repository" to a static value that is identical for all issues from the one GitHub integration. That way we could then show the value as a label and also filter by it in feature vi...
Guest
over 2 years ago
in GitHub
0
Future consideration
From the release details, on the integrations, allow sending (and re-sending) all features in the release to GitHub.
Currently, one needs to manually send each individual feature to GitHub when starting a new release, which can take a really lon...
Tiago Sousa
over 4 years ago
in GitHub
2
Already exists
Our QA team has a hard time seeing the story of a ticket due to all of commit messages. It would be nice if instead of appearing as just comments the Github commits appeared separately or were able to be be filtered out.
Guest
almost 5 years ago
in GitHub
0
Future consideration
GitHub Commit Hook shouldn't add commenting user as a watcher (or shouldn't run as user)
When the GitHub Commit Hook is run, it adds me (the user who created the integration) as a watcher on whatever features are referenced. This becomes a huge notification nightmare pretty quickly.
It would be great if the comments on features as a...
Guest
about 5 years ago
in GitHub
0
Future consideration
Change GIT Integration to Separate from Human Comments
Right now all GIT commits (with task IDs) are populating the human comments. Ideally, this would be in a separate list, so there's not so much noise in the comments.
Guest
about 5 years ago
in GitHub
1
Future consideration
As a new client I setup the Github 2.0 integration and imported our existing issues as features.
I now have a large task of organising them all from the the parking lot and would find it easier and more intuitive if the IDs of the Aha! features wa...
Guest
over 5 years ago
in GitHub
0
Future consideration
Fix Github Integration action buttons / support custom name
currently the github integration supports multiple repositories for a project, however I cannot distinguish between repositories in the action buttons http://take.ms/cLrzK , Use the repository name: Send to githuborg/reponame or support custom int...
Gabo Esquivel
over 6 years ago
in GitHub
3
Already exists