GitHub

This is how things works in reality for complex applications. We have a very modular architecture for a product. ( micro services ). One product can have up 10 repositories. Even the simplest application would have frontend and backend repositorie...

When I send a feature to Github that has images attached, the images show up in Github as links rather than inline which is how they would show up if I had created the feature in Github. It's easier and cleaner for our developers to see the images...

The intended use of GH integration is the following: Create features in Aha Push to GitHub as a handover of control to engineering Updates in GitHub trigger status changed in Aha This is a good start. If control is passed to engineering to manag...

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...

I am currently utilizing Aha! and have it linked to several of our team's Github repos. The functionality to create issues in Aha and send to to Github works great. However we often have cases where issues get created in repos directly. When those...

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.

Github integration messages in comments is great for smaller stories, but for anything non-trivial it becomes very easy to lose meaningful comments in the middle of a commit barrage. It would be very useful to have these either separated, or group...