We typically reference feature requests by the Aha feature ID, e.g. WEB-32 or WEB-44. When we push those feature requests down to Github for development, we generally create a branch for each issue, but since we lose this information it's difficul...
David Bean
about 8 years ago
in GitHub
2
Unlikely to implement
If you add Github Issues integration with a Github account that requires 2-factor authentication, the integration fails. It would be good to support this.
Guest
almost 9 years ago
in GitHub
1
Already exists
What is the challenge? GitHub is introducing support for Issue Types In beta/previous mode currently https://docs.github.com/en/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization https://github.blog/ch...
Scott Vonderharr
about 1 month ago
in GitHub
0
Future consideration
The importer shows all repository issues, including closed issues. It also doesn't show what the issue status is, so we must click through them to find those we want to import. I suggest: adding a status filter, set it to show open issues only sho...
Alexey Zimarev
8 months ago
in GitHub
0
Future consideration
Who would benefit? Anyone with a GitHub Integration What impact would it make? Right now, the syncing of an Aha! Item Requirement's tag is not supported. This means any requirement that the visibility of tags on a requirement is lost in GitHub if ...
Guest
11 months ago
in GitHub
0
Future consideration
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
over 1 year 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 3 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 long...
Tiago Sousa
over 5 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 6 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 6 years ago
in GitHub
0
Future consideration