We spend all that time estimating and have to reproduce the work when we send the stories to TFS. Please! Make it stop! Setting to a month because this seems like a no-brainer!
Add a tag to requirements, and sync it with jira labels
Why is it useful?
Our Product team uses tags in Aha and labels in jira to help in planning which team works on which requirement / user story, to make sure that one team working in the release is not over-burdened.
Sometimes one team works on an ...
TFS (a.k.a. VSO) Automatically create new stories in TFS as requirements in Aha! when stories are created under a linked feature.
If a feature has been sent to TFS as a feature and requirements as stories, when I create a new story under the linked feature I would like it to be automatically created in Aha! as a requirement.
The integration with TFS has a lot of potential, but it's still work to have to remember to click the Action then Update TFS. If some product owners forget, then we have to audit what features and requirements are in both systems and see which one...
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.
Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...
Currently you are able to send features to Trello from Aha and their status will be updated as they are moved in Trello. However comments and attachments that are added to Trello cards/features do not move to Aha. Enabling this feature would allow...
We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets. It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages indiv...