Ability to update Jira Affects Versions field from Aha via integration
What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner
about 1 year ago
in Jira
1
Future consideration
Integration between Aha! and SPM module of ServiceNow
What is the challenge?
Several teams in our org are using SPM to manage their project works and roadmaps, and they are seeking for easy way of integrating those data within the tool with Aha.
What is the impact?
No integration tool to easi...
Hank Liu
3 months ago
in Integrations
0
Future consideration
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf
over 3 years ago
in Integrations
4
Future consideration
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest
over 6 years ago
in Jira
6
Future consideration
Create Standard Integration to Send Ideas from One Aha! Workspace/Account to Another
What is the challenge?
Different Aha! Workspace in other Aha! Accounts cannot communicate except through a manual import of data or API.
What is the impact?
At larger companies, it is not always feasible to use one Aha! account. We current...
Development Integration -- Support rendering of images embedded in description field
Currently when you import from Jira or Azure DevOps, if you have images embedded into the description field, they come over as a link in the Aha! description field, e.g. imagename.png. It would be great if they would render in Aha! like they do in...
Our company is looking to adopt WorkBoard as our corporate standard for OKRs. Our development business units use Aha to manage our product strategy and roadmaps so we need to have integration between the 2 systems in order to maintain continuity o...
Joe Granville
about 5 years ago
in Wanted
3
Future consideration
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
about 10 years ago
in Jira
17
Future consideration
Include history of comments when importing from ADO integration
What is the challenge?
Currently, when importing ADO records via an ADO integration only the latest comment is imported from ADO
What is the impact?
Inability to see comment history can lose critical context and require Aha! users to go to...