We receive a number of ideas that are different enhancements to the same product element or function. I typically create a single feature to improve the functionality of X and the various ideas become requirements of the feature. It would save time to turn these ideas into requirements instead of just linking; it allows my developers to focus more on what needs to be built.
You can now promote an idea to a requirement in Aha! Roadmaps. This gives you more flexibility when when working through customer feedback.
Also wanted to mention that the feature https://big.ideas.aha.io/ideas/APP-I-3071 marked as shipped doesn't seem to work. If I workaround and promote to feature then convert to a requirement, the link is lost between the idea and the requirement.
Just looking for some clarification - the promote option allows me to promote to Master Feature (Epic), Feature or Initiative... I don't see where you can create a requirement/user story against an existing feature with what was recently released?
This is basic requirement for a product management tool and it's amazing to see this is 5 yrs old with no action.
A lot of extra clicking and manual tracking of the Idea after I've converted the promoted Feature to a Requirement. Idea's come in all shapes and sizes, including Requirements.
Do it! It's easy enough to promote to feature and then convert to requirement, but what is lost is the ideas association/link to the actual 'workable' record (like feature) and therefore the idea isn't automatically shipped once the requirement is - we have to manually track and close these ideas out. As a workaround, we set a to-do on the idea which references the requirement and set the due date to when we expect the requirement to ship, so we get a notification which serves as a reminder to ship the idea (presuming the requirement has actually shipped.......
This is definitely causing a time sink at the moment. Coming from ProdPad into Aha! I'm feeling the pain of all the unconnected elements which I had in ProdPad (at a previous company).
Please consider this, it will save a lot of time
We also need the ability to Promote Ideas to the Requirement level. Allowing users to group a number of Idea Promotions under the same Feature (w/o Idea merging). Some decisions will need to be made around the creation of a dummy Feature level object will be required.
This is a great idea - a lot of the time the idea itself will form a requirement of the Feature.
Agreed - we often get ideas that are enhancements to existing features or we will culminate a collection of ideas into a single feature with each of the ideas being a requirment
Yes, we would like to see this option as well, we don't always want to capture an idea as a large chunk when it's a small enhancement and can be grouped with other ideas.
Agreed. We are in need of the same.
This would be super helpful! Agree with others that the majority of ideas we receive fall under a feature/epic as a requirement, not as a feature itself. I'm in the process of convincing the company to move towards Aha! for all our needs and this will help prove that it's a seamless place to do our work! I'm promoting that Aha! requires less steps...having this ability will help prove my point!
This will be so useful!! Can we have this please AHA!
NEED THIS TOO! Sad that this is in such high demand and has no movement by Aha!. Boo.
We would love to have this to move ideas into features that already exist.
I like this one!
This would be a fantastic addition. I agree with the comments on this Idea, most of our submissions to the Idea Portal support either an existing Feature or would be part of a new Feature. The manual work of copying the Idea information over to a Requirement when we do want to promote an Idea can be a nasty time suck.
Our team desperately needs this functionality. We need to promote ideas as feedback like "Change this button" that aren't really the scope of a feature, they're just a task that we need to get done and track that it's shipped.
would be great to have this functionality! We have lots of small ideas that don't deserve being called a "Feature". These are often small enhancements and are only sub-tasks in JIRA.
It is currently a pain to manually update the status of such ideas.