promote an idea to a feature requirement

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.

  • Karen Wittenberg
  • Nov 3 2016
  • Future consideration
Release time frame
  • Attach files
  • Stephen Morse commented
    March 20, 2017 18:39

    Please do this, it will help us get our small ideas merged in as requirements to a parent feature. 

  • Allie Seymour commented
    April 11, 2017 17:37

    Agreed. Most ideas support a larger epic/feature, and it would be very helpful to promote an idea as a requirement and link the status updates to the status of that requirement. This will also help greatly reduce the manual status updates for promoting many ideas to the larger feature

  • Allie Seymour commented
    April 11, 2017 17:37

    Agreed. Most ideas support a larger epic/feature, and it would be very helpful to promote an idea as a requirement and link the status updates to the status of that requirement. This will also help greatly reduce the manual status updates for promoting many ideas to the larger feature

  • Brad Houser commented
    May 30, 2017 14:15

    YES! YES!  YES!  please do this soon.  Not everything is a feature.  Many of our employees are submitting bugs into the idea portal.  these are not new features.  We also have people submitting requirements, not features. 

  • R Burrows commented
    May 30, 2017 14:30

    I couldn't agree more. Please implement this idea posthaste.

  • Courtney Cohen commented
    May 30, 2017 14:42

    Glad to see this is likely to be implemented. Almost all ideas submitted here are bugs or stories, which we log at the requirement level. This would streamline our process and ensure we don't lose any items in the multi-step process of converting from idea to feature to requirement etc.

  • Anum Qassam commented
    October 20, 2017 14:00

    Really important for us! Please implement!!

  • Randy Barnes commented
    November 14, 2017 16:35

    This would be awesome!  Gives more flexibility to convert an idea into anything withing the Product lifecycle

  • Jeremy Fiel commented
    December 01, 2017 16:54

    any update on this enhancement?  

  • Teresa Abraham commented
    December 01, 2017 20:09

    We need this enhancement to be efficient with how we create features vs. Epics for new enhancements. It is very time consuming to promote to EPICS first and then convert to features

  • John Bacus commented
    December 20, 2017 15:29

    I just ran into this one- I think it would be really helpful. Right now, the best workflow I have is to promote an idea to a feature, then convert that feature to a requirement of another pre-existing feature.

     

    In my experience, most users request incremental improvement to existing features most of the time. It would be great to be able to support these better in Aha.

  • Xiang Wu commented
    February 01, 2018 17:55

    really important!!!  also we would like ideas to be mapped with bugs in JIRA as well.   

  • Tom Beck commented
    February 16, 2018 23:14

    When implemented, this should include promoting an idea to both a new requirement or to an existing requirement.  (Perhaps that just goes without saying).  

  • Eric Brown commented
    August 10, 2018 13:19

    This feature would be incredibly useful so that we can maintain links between Salesforce cases/opportunities and JIRA issues (once we promote the feature/epic and its requirements/stories to JIRA for development).

  • Beth Burke commented
    October 01, 2018 06:36

    Agree - this would be extremely helpful.

  • Angad Singh commented
    November 07, 2018 21:16

    +1 to the Idea. Not all Ideas are Epics ( Features) some are just enhancements to current functionality and should be treated as User Stories

  • Laura Owusu-Antwi commented
    November 20, 2018 19:26

    100% agree

  • Robyn Diamond commented
    December 11, 2018 21:21

    Adding to this - sometimes an Idea comes in & it's small enough in scope that it can simply be added to an existing Feature within the next Sprint. 

    OR we have a container-type of Feature for task-like requirements to be completed. 

  • Gil Blustein commented
    21 Feb 21:00

    Please consider this feature. It will help us promote ideas and get them into the backlog. Otherwise, its just a difficult process

  • Jens Schulz commented
    28 Feb 21:22

    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.

  • Charles commented
    30 May 16:31

    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.

  • Mark Grundman commented
    19 Jun 13:25

    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.

  • Damian Brown commented
    20 Aug 03:37

    I like this one!

  • Rich Cernech commented
    21 Aug 20:01

    We would love to have this to move ideas into features that already exist.