-
Allow children of integrated items to remain not integrated until ready
I integrate our epics (master features), features, and PBIs (requirements) with DevOps (previously known as TFS). Often, I want to insert a new PBI (requirement) but I don't want it to be pushed to DevOps until it's fully built-out and ready for ...3 Future consideration
-
Enable Field Filters for when to Sync to Aha
I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...0 Future consideration
-
Integrate Aha! and Confluence to link Confluence Pages in AHA! and transfer them with JIRA
Atlassian currently offers the ability to Integrate Confluence & Jira using Application Links which gives teams multiple features. https://confluence.atlassian.com/doc/use-jira-applications-and-confluence-together-427623543.html One of the fea...3 Future consideration
-
Event dimensions and metrics for GA integration
I was playing around with the GA integration for Aha for Product. It’s good but I noticed there weren’t any dimensions or metrics around event tracking. As a single page application we rely heavily on events and it would be great to be able to add...1 Future consideration
-
Link Salesforce opportunities to Features
Today, the SFDC integration can only link opportunities to ideas. It would be great to also link to features. This could help prioritize features that are still in a parking lot and would reduce the buden of merging ideas created via SFDC with exi...0 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 ...0 Future consideration
-
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...0 Future consideration
-
Support "Agility" (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" ...6 Future consideration
-
Allow for a check list to be copied to the GitHub product AND not change the check list in the originating work activity.
The check list (versus ordered / unordered list) in the text field is very nice. However, integration process translates the Check List to an unordered list in GitHub and then updates that back to the originating work activity. This process cha...0 Future consideration
-
JIRA Integration: Adding Master Feature, Initiative & Goal Record Links
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...1 Future consideration