The current functionality to promote an idea to either a feature or an initiative is fantastic but there is a use-case for when promoting ideas to releases would be extremely useful.
Marketing teams will often create an ideas portal in order to collect ideas and suggestions from internal teams and market partners on new campaign ideas. These ideas will then be prioritised and promoted to releases in Aha! where a number of digital assets will then be added to the releases as features which the creative teams will then build.
Currently an an idea can either be promoted to an initiative and then mapped to a release in a 1:1 relationship (unnecessary overhead and the initiative contains the information rather than the release) or as a feature within a campaign (which then goes in with all the digital assets that need to be created and technically isn't a feature).
In this instance promoting to a release really would make sense. I would imagine other teams such as Sales could also benefit from this functionality. Thanks!
Like Robby McWilliams we'd like to capture solution ideas that solve problems, where the solution is a whole "Release". From a Design Thinking perspective this is essential. We will most likely do that more often than promoting to e.g. a "Feature", in our product journey.
Ideas to Releases are how we think of introducing value to the market. The ability to promote an Idea to a release would allow us to use Aha in a way that aligns with how we do business.
This would be extremely helpful for our team. Some of our ideas that are coming in are enough to warrant a new release/new product to be added to our roadmap.
We work in marketing, we call ours projects, and activities. We would like to have the ability to promote ideas to projects as well as the other options provided.
We use Aha for Intake and it would be extremely helpful to be able to promote to a Feature.
We copy and link Ideas to the team that is going to work on the ticket, so it goes into their Ideas workspace. From there it would be helpful to promote to a Feature. Since they can't they have to recreated the ticket as a Feature. Now the link to the original ticket is broken unless they link to two together. It makes for a very cumbersome process when dealing with a lot of Idea intakes and teams.
some ideas are large - and when we begin to design they will be broken down to epics underneath a release.
This would be really helpful for our team, as we want to records ideas for things we are not yet working on. Once an idea is prioritized, it would become a release with set timelines.
This would be beneficial as it would allow the team to actively see what ideas are being worked on. It would also help as currently promoting to an activity within a loosely related release means changes aren't easily monitored.
I'd like to echo this suggestion and fully endorse this being added, i can only promote to an activity (which gets added as a feature within a release) an Epic or an Initiative. This would really improve the functionality of the application and reduce effort or re-work by users.
Yes please for this one! for new workspace types (particularly project workspaces) we prioritise ideas then put them onto the roadmap as a schedule. Currently we can't mark the idea as complete when that release/schedule is completed.
This would be really beneficial for us as our Idea submitters have no understanding of the sizing of what the are submitting. Meaning that they can be as small as a features or as large as an initiative or anywhere in between - meaning they could likely be Releases. It seems odd that you can promote to Feature, Master Feature and Initiative but not Release.
We are collecting requests and ideas from our sales team through a portal. Every project we do will be a release in Aha for various reasons. Right now we have to create the project manually and loose the connection with the idea.
To workaround the lack of this feature, we've been using the linking of records to say an idea is `contained in` a release. While not as good as the idea, it helps provide the data-relationship.
As a PM team, we define criteria per release, giving engineering and design room to own the "how" is best to solve it. Thus we often find ourselves looking to promote to a release (where we do a start of a hand-off) so they can own writing the feature stories, but understand the needs.
This would be very useful for us as well.
We are using the release as a milestone, and it's a blocker for us not allowing convert idea to a release/milestone please advise if there is any plan to integrate this option soon.
Would be a big + allowing us to promote ideas to Releases as we use these as Milestones and would be an ideal way to get that initial idea in front of the teams prior to having a more mature milestone.
This would be extremely useful in our team. We use releases as projects and the portal to request projects.
Hi Lisa, in most use cases we have heard it would be better to promote the idea to a record within the release (e.g. epic or feature) vs the release itself thanks to the additional capabilities of those record types. For example, one option for ideas that represent larger projects would be to promote those to master features. This would allow you then break down individual features that all map back to the master feature -- either contained in a single release or spread across multiple releases.
I'm interested in knowing why this was marked as "unlikely to implement"? We're using Ideas as our opportunity backlog and sometimes these as well as user-submitted ideas are actually full-on projects rather than simply features. Being able to promote to a release (or even a product!) would be very useful.
Would be a huge benefit for our team - I am happy to walk through how!