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
What is the challenge?
I would like access to TestRail results and Github information in Roadmaps
What is the impact?
Team members that don't have access to Aha Develop cannot see this data.
Describe your idea
Please allow extension ...
Devin C
5 months ago
in Integrations
0
Future consideration
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
almost 5 years ago
in Wanted
3
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...
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
When linking an Aha! record to an existing Jira record, perform a full sync of all fields
What is the challenge?
When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...
Leigh Villalovos
7 months ago
in Jira
0
Future consideration
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...
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R
over 2 years ago
in Jira
2
Future consideration
Enable Aha Roadmaps Confluence Cloud macro to support 'static rendering'
What is the challenge?
The Confluence macro for Aha Roadmaps is no longer insertable inside other macros such as filterable table macros, as was possible in Confluence Data Center. This is due to a requirement for 'static rendering' support in C...
Guest
4 months ago
in Integrations
0
Future consideration