GitHub Integration: Aha! Release to Github Release mapping
As a product manager setting up my GitHub integration, I want to map Aha releases to GitHub releases directly, to avoid confusing developers and make Aha adoption less painful.
Guest
over 4 years ago
in GitHub
0
Future consideration
Provide the ability to ingest issues created directly in a linked Github repository
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...
Guest
almost 7 years ago
in GitHub
0
Unlikely to implement
GitHub integration automatic log time upon linked issue completion
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...
Add the ability to combine fields with GitHub Integration
We need the ability to send more information from Aha to GitHub, this would include the Due Date. We need the ability to combine fields from Aha to a single GitHub Field. E.g. Send Title + Due Date in Aha to the Title Field in GitHub - somet...
George Champlin-Scharff
about 5 years ago
in GitHub
0
Future consideration
Update GitHub Repo mapping when Repos are moved or renamed
GitHub makes it easy to rename and/or move a repository to a new owner / organization. In the UI (and all git tools) it smoothly handles this for users, automatically redirecting you to the new location. As a result, people move projects on a fair...
George Champlin-Scharff
about 6 years ago
in GitHub
0
Future consideration
Allow for a check list to be copied to the GitHub product AND not change the check list in the originating work activity.
The check list (versus ordered / unordered list) in the text field is very nice. However, integration process translates the Check List to an unordered list in GitHub and then updates that back to the originating work activity. This process change...
Guest
over 4 years ago
in GitHub
0
Future consideration
Allow Relating Multiple Github repositories to a Single Product
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 repositori...
Gabo Esquivel
over 6 years ago
in GitHub
4
Already exists
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
We use the Github integration for a few of our projects. I have it configured to import Features to Issues and Requirements to Issues.
It would be very helpful to exclude some records during the import process. For example, I recently sent a Featu...
Guest
about 5 years ago
in GitHub
1
Future consideration
Mockups are being sent to github as links, opening the image externally, instead of showing them directly in the issue. Prepending the link with an exclamation mark would show the mockup inside the github issue, a much useful approach.
Current mo...