It would be great if we could have Initiatives sync over to TFS as Initiatives or Epics to get the full hierarchy tracked in both systems. As it stands, we have to manually create initiatives in TFS and then link the Features up to them. Adding it...
Support the "links to" field mapping with next-gen templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates.
Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" ...
Support for "Select list (cascading)" field type in JIRA
JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...
Salesforce Integration Merged Ideas also should merge Opportunity List
I'd like to request when an idea is merged that its Salesforce Opportunities are merged as well. Presently, the behavior I have observed is that merged ideas still retain their distinct opportunities linked from the Salesforce opportunity. As a us...
Andy Pendergast
almost 8 years ago
in Salesforce
4
Shipped
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!
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...
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...