Integration with TFS 2015 on prem which includes the Rest API: https://www.visualstudio.com/en-us/news/tfs2015-vs.aspx#restapi This is the first release that brings REST APIs to on-premises TFS.
As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release
Make Github integrations support Github Enterprise
The existing Github integrations are splendid but only works for Github.com. For those of us running Github Enterprise we need to be able to configure our Github API endpoint as well.
As far as I know changing the API domain should be the only thi...
Choose the MRR value at the account level when creating ideas from salesforce.com
Can we map the value field to an existing account field for cases? Value is automatically pulling from the opportunity and we actually have MRR at the account level and it would be great if we could map that for cases.
Melissa Hopkins
almost 10 years ago
in Salesforce
0
Shipped
JIRA Import multiple issue types as requirements mapped to parent feature
As a PO, I’d like to import multiple issue types (i.e. bug, story) as requirements that map to their parent features so that existing Jira Projects can be imported into Aha! Products in a single import
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 ...
It would be useful to be able to send requirements to different integration points. i.e. if we use requirements for a design task these could be sent to Trello. and Development tasks could be sent somewhere else - Jira. Or to two different project...
Guest
about 10 years ago
in Integrations
1
Shipped
Improved automatic pull of items from Jira to ensure strategic relevance of Aha!
As a product manager with an engineering team that uses Jira, I understand and appreciate that Aha aims to remove the temptation for anyone to "sneak" tasks into Jira rather than through the PM and Aha!. The reality, though, is that agile sprints ...
The way Aha is explained and shown in the support files and sacreenshots, the aha 'features' should be backlog items in TFS under the SCRUM template, not VSO Features. Until we hit this, Aha was wonderful.
Guest
about 10 years ago
in Integrations
2
Shipped