Request Aha! Integration with RealtimeBoard Merged

Thank you for letting us know! I have merged this idea into the related idea for a Miro integration.

Hey, you guys have a separate integration request from this one for Miro, RealtimeBoard is now Miro, so these should be merged I think.

I think this would be an excellent addition to the Aha product, particularly to complement the new Empathy Session feature. We've been using Miro like crazy during COVID to facilitate virtual design sessions with each other and with customers and have loved it. In addition to what the requestor of this idea described, it would be nice to be able to move from an ideation or voting session based on feedback in the empathy session, which is where Miro (formerly RealtimeBoard) would come in.

SketchUp team provided a demo of Realtime Board with Amy Woodham to demonstrate Product Management use of Realtime Board and why an integration of Realtime Board with Aha! is of great value;

Idea promotion to a Feature while available in Aha! is structured & only addresses the Feature field.  We work in Realtime Board with Features as well as a hierarchy above a Feature such as Themes, Initiatives, Goals, Objectives, Master Features, & Dependencies - our Product Management, Product UX, & Engineering go to Realtime Board prior to Aha! via concept ideation, solution proposals, feasibility design workflows modeled in Realtime Board for a greater fluidity in solution proposals.   The efficiency in linking/sending this information directly to Aha! would build efficiencies in our work.  

Use Cases for use of Realtime Board are both Upstream & Downstream; 

- Downstream - Release Planning & Sprint Planning - the 'big picture' visual of having everyone in the same tool to contribute to planning for our Master Features/Capabilities Plan.  Product Management, Engineering, UX/UI, & QA need to identify Features, Requirements/Stories & be able to move them around/prioritize freely proposing different paths to enable our Master Features.   

- Upstream - Ideas / Concept Phase - Architectural / UX impacts - PI Planning 

*In both cases once consensus is achieved on the solution approach then integration from Realtime Board to Aha! would drive organizational efficiencies and accuracy in tracking of information.   

Note the following links pertaining to Realtime Board use and integrations; 

Architects, Product UX/ UI, Product Management all use Real Time board in some cases for complex roadmapping, design workflow, with product features and requirements that naturally fall out of these workflows where integration with Aha! would allow for mapping of Master Features, Features, & Requirements rom RealTimeBoard to Aha!  Currently, it is dual entry and we have Product Managers who are cutting Aha! out of the mix as it RealTimeBoard integrates with Jira & not Aha! 

Agree, we do a lot of upfront design work and this process is iterative across sites, so RTB is essential. Being able to push master features and features easily into Aha! would be awesome

Thanks for updating status on this idea
. Comments and Votes are
coming in from my teammates - please continue to keep this one on your
radar as it would draw A LOT of efficiencies here and I bet a lot of other
places too!

The following Use Cases support an Aha! Integration with RealtimeBoard / RTB for automatic/efficient creation of Master Features, Features, & Requirements as a result of the following activities that take place in RealtimeBoard; 

• RTB Conceptual / Idea planning to Design (Master Features & Features <-> Aha!) 
• RTB Release Planning (Master Features, Features, & Requirements <-> Aha!) 
• RTB Sprint Planning (Features & Requirements <-> Aha!)