Need Aha! Requirement --> Github Issue and EXCLUDE Aha! Feature --> GitHub Issue
If you look at an Aha! Feature as a container of requirements, e.g. Aha! Feature with 3 requirements, then when you send a in the : Feature—>Issues, Requirements —> Issues; then you end up with 4 issues in GitHub - when you only need 3.
...
Jonathan Ross
about 8 years ago
in GitHub
2
Shipped
The ability to do a bulk import exists, but if the issue already exists in Aha! it does not re-import. It would be useful to have the ability to alternately do a bulk update. This is particularly useful in the off chance something breaks with the ...
Slack recently launched 'actions' that allow users to do things with messages, similar to built-in actions like adding reactions or message sharing.
These custom actions provide a simple and visual way for people to interact with an app from Slack...
Given that a PM controls their backlog and roadmap from AHA it would make sense for them to be able to do more than simply send the story to VSO and be subject to changes that are prompted only from VSO to AHA.
For example, if i decide that a feat...
Add support for TODOs in the Activity WebHook integration
We use several tools for keeping track of different types of work items (TODOs), such as Trello, Aha and VSTS. I would like to be able to extract the TODOs from Aha so I can create an integrated view of pending work. Since there are many types of ...
Harm Pauw
over 7 years ago
in Integrations
2
Shipped
Better requirements link handling in Jira integration
From the Jira "READ SECOND" blog post: "If a new issue is created in JIRA that belongs to a record that is already link to Aha!, then the issue will be automatically imported to Aha! This applies to issues created under a version, stories created ...
Aaron Bawcom
almost 10 years ago
in Features / Jira
1
Shipped
Enable ability to create autolinking rule for Gitlab/Github
GitLab drops the product prefix, and only supports a single hardcoded URL which means setting up an autolinking rule from Gitlab/Github to Aha! is not possible.
Two Way Jira Sync for Initiative/ Epic custom fields
As far as I am aware you can only map feature custom fields, and I'd like to be able to maintain due dates, team and other custom fields at the Initiative level.
Currently, we need two Jira integrations - one for Bugs, and one for everything else. But when importing/linking Bugs, they get linked to a regular ol' Feature of "New" type.
As someone in this situation, i want imported/linked Jira Bugs to set t...
Right now there are a few apps that offer message actions right in slack, for example I can send a comment to Jira immediately by hovering over a message, selecting "more actions", and selecting "Add to Issue". It would be awesome to have somethin...