Ability to map idea statuses to feature statuses

I would like the ability to choose how my feature statuses map to idea statuses so when feature statuses change, that I have mapped to an Idea status, the idea status also changes (and changes in status notify subscribers of ideas).

  • Chris Waters
  • Dec 4 2014
  • Planning to implement
Release time frame
  • Attach files
  • Gord McNeill commented
    April 13, 2015 16:56

    Yes,  the current mapping is not enough,  we need more granularity.   for example, when a idea is converted to a feature that does not mean that it is in progress,   i need to leave the idea status as is, until work actually starts.

  • Jeremy Naiden commented
    May 13, 2015 13:28

    Yes, +1 on this!  As we're using this more and more and seeing the value of the ideas portal, this is huge.  A classic example for us is something like "Reviewed and Waiting".  This is an important piece of the communication loop back to the original requesters.  Thanks to the Aha! team for considering this for future implementation.

  • Jeremy Naiden commented
    June 03, 2015 20:48

    Going to throw another comment at this.  The idea status updates driven by the feature status updates as currently implemented are not nearly as useful as they could be.  To communicate with idea submitters effectively, we need to be able to map the updates from features to ideas.

  • Ross Reynolds (External) commented
    September 15, 2015 22:14

    This is one of the main impediments to using the Ideas Portal for us.  Nobody knows where their ideas are, and it's too much for the POs to keep the features and ideas lists in sync.

  • Guest commented
    September 24, 2015 13:52

    +1 I would really like to encourage my "idea community" to go in an test on our DEV/QA regions when something is ready...  I'd like it to follow the same model as a feature (+ Will not implement).  

  • Dale Burnett commented
    October 27, 2015 17:29

    Agree this would be a very useful feature for the system.

  • Guest commented
    March 14, 2016 09:59

    This is one I think would be a nice easy one to address provide big value to product managers and customers. We need to take the manual work out of this process by allowing more mappings to keep our customers updated.

  • Alejandro Lopez commented
    May 13, 2016 09:26

    Are we asking for this improvement since 2014 ?

  • Peter Marshall commented
    August 09, 2016 21:12

    Wow, I really can't believe this isn't already a thing!  I'm not being grumpy, I just assumed it would be a must-have experience of tying an idea to a feature.  I wonder, does the Aha! team manually update the status of an idea in this big ideas forum when, for example, it changes from "Likely to implement" to "Planned" or from "Planned" to "Shipped"?

  • David Kettinger commented
    August 26, 2016 15:54

    Totally agree that this would be of tremendous value both as a communication mechanism and as a major time save for not having to manually update idea status based on what is happening with the feature.

  • Admin
    Chris Waters commented
    August 26, 2016 23:20

    It is worth noting that idea statuses do update automatically based on feature status to a limited degree. This is described here: http://support.aha.io/hc/en-us/articles/206688256-How-feature-status-drives-idea-status

    This idea is still relevant, but I wanted to point out the existing functionality since some of the comments here imply there is no relationship between idea status and feature status.

  • David Kettinger commented
    August 27, 2016 01:39

    Chris. Understood that there are some relationships (well 2 anyway) that drive idea status relative to a feature. That is very useful. It would be much more useful of there were more. It’s actually surprising that there isn’t given that there are 4 status categories and only 2 of them (In Progress and Done) relate to any automated status change action. It’s unclear what if anything the other 2 status categories (Already exists and Will not do) are used for.

  • Ross Reynolds (External) commented
    August 28, 2016 20:34

    Thanks for the update Chris.  I'll echo Jeremy & David's comments that while the ability to automatically trigger "planned" and "done" is there, it doesn't really map to our usage.  When we promote an idea to feature, it just means it's valid and in the backlog where we can prioritize against other features.  It still make take weeks or months to be committed.  It would be good to be able to update stakeholders when it is approved, planned, then actually in development, Anyway, we've moved on and aren't using the ideas portal to update stakeholders, but just wanted to pass the feedback along.  If we had this, it would get more usage.  

  • Tom Beck commented
    February 15, 2017 20:25

    Now that I have voted on this and brought the total count of to 75, let's get moving on it. :)

  • John Brickell commented
    June 05, 2017 15:30

    This is an important capability for us to fully utilize the Ideas portal status within our workflow.

  • Guest commented
    June 05, 2017 16:16

    In an organization with 1000 SE submitting idea you cannot live without this feature.

  • Geoffrey Kim commented
    June 05, 2017 17:50

    I'm glad that I'm not the only one to see the improvement!  We can make the Ideas Portal a better aligned with flexible linkages to promoted features.  Definitely +1!  Thanks!

  • Devik Lansing commented
    June 30, 2017 15:31

    We desparately need this idea to be implemented.  In our flows we need to make sure an idea submitter realizes that the feature has been abandonned/will not do.  

  • Paulo Branco commented
    July 04, 2017 17:26

    Totally agree with this ! This also has a huge influence on JIRA -> features integration.  I want to only show my idea in progress AFTER a JIRA story development starts. With the current Aha design this is not possible. Moving an idea to a feature automatically marks that as 'in progress'. (I created another status to avoid this). 

  • Paulo Branco commented
    July 04, 2017 17:32

    When is this item going to be released? 


  • Markus Standau commented
    July 14, 2017 09:37

    In the default workflows, once an idea is promoted to a feature, its status changed to "planned" , but on the feature workflow at this time, it's not really assess and there is a chance that it will be determined to not implement this feature, so the status of the feature can be set to "will not implement". At this pint the idea status is NOT changed, and it keeps dangling in the "planned"status.

    Therefore this enhancement request makes a lot of sense, because

    • I would want to chance the idea status not when promoting to a feature, but only, when the feature is assigned to a realeres or maybe the parking lot
    • The idea status also needs to be changed in can of a feature that was once planned, but later gets scrapped an is changed to will not implement 
  • Precious Curtis-De Vance commented
    August 15, 2017 23:23

    I ditto the necessity to have this functionality.  This is a manual hole in the process of Idea/Feature synchronization and knowledge.  Please add this to your next release.

  • Guest commented
    November 21, 2017 17:03

    It is upsetting this was submitted nearly 3 years ago, but has not been implemented yet.

  • David McElroy commented
    December 19, 2017 14:31

    As with other posters, when an idea is pushed to a Feature, it doesn't mean that it is in progress.   We need more status updates since the majority of our stakeholders will only be accessing the Ideas portal.  Without more status updates, we will be tasked with more reporting to keep individuals updated on their ideas they submitted.

  • Mark Brown commented
    February 16, 2018 20:18

    +1 too.. need to be able to better sync status between ideas and features, so the idea has an accurate representation of current status.. Accepted, is fine, but I want to be able to update when the idea is scheduled for release and also once development starts...

  • Mark Brown commented
    February 16, 2018 20:20

    What does 'planning to implement mean'? Is there a timescale for this yet?

  • Dave Tucker commented
    April 20, 2018 10:22

    Agree. As we expand the use of Aha and force more ideas and requests through the process this is a major gap. Ideas raisers are left wondering where their ideas are as there is a large gap between promotion to a feature and delivery

  • Sam Marsh commented
    April 27, 2018 14:52

    +1 on this, also. This is a big gap.

  • Greg Koeka commented
    July 19, 2018 17:08

    It would also be great to have the Idea status change for internal stakeholders when it's promoted. Example: I promote an idea and the internal stakeholders will see the idea status auto change to Promoted to Roadmap or some other status determined by the Admin. Then it follows the Dev status mapping between the Dev tool (JIRA, Rally etc) and Aha!. This would allow other stakeholders watching the idea to get updates automatically on it's progress. 

    Given that even years can pass by before something gets worked on, like this feature for Aha!, getting updates are paramount and provides value to those stakeholders...in this case Aha! customers.

  • Joe Carpenter commented
    October 29, 2018 16:55

    Any update on this? Seems like it has been kicking around for a couple of years at this point.

  • Jonathon Mavin commented
    November 15, 2018 00:48

    100% yes I would really value this feature. 
    As Aha! is all intertwined its really hard to get a 12month roadmap without having the Ideas loaded up as Features and then the features into Releases so that we can have a 12month visual. 
    So I've had to move promote a lot of ideas to features - the communication channel I'd like to use for progress is the IDEAS portal so that the people who are supporting the Idea get more status updates than "planned or shipped"... so they can keep their stakeholders advised of their ideas progressing through the stages. 

  • Robyn Diamond commented
    November 26, 2018 21:38

    SO MUCH YES! We have multiple statuses prior to In Progress, then In Progress, then Done. I'd like to provide greater transparency by choosing which Idea Status maps to a Feature Status & have it auto-update. It would save our teams so much time!

  • Dan Fiore commented
    December 03, 2018 12:59

    Please develop this feature

  • Rachel Goldberg commented
    December 03, 2018 15:36

    Adding my feedback that I'm surprised to learn this isn't how it already works, and not having this undercuts the value of having a single platform for idea and feature management. 

  • Robyn Diamond commented
    December 12, 2018 21:04

    A big part of a PM's job is close the feedback loop to customers, however, automation of that loop saves valued resources and critical dollars for our company.

    In JIRA, we had this ability between Request & Work projects which streamlined PM daily tasks & provided real-time updates to customers. Without it in Aha!, Idea tickets are outdated & customers are continually reaching out for updates - losing us time that should be spent on other projects. 

    Additionally, according to the Aha! KB: "Promoting an idea to a feature or initiative causes the status of that idea to change to the first status that's in the category "In progress" We have multiple statuses in an 'In Progress' state. To move to the first one most likely is irrelevant so again, I'm seeing inaccurate data & wasted resources to update. 

  • Eric Huber commented
    17 Apr 18:50

    The status on Idea is not granular enough. We would like to see the Idea Status mapping to Jira Status as close as possible. The main driver for us to use Aha is to reflect the status of the request. Not able to do this really defeat the purpose for us to adopt this tool. 

  • Kevin Mowry commented
    10 May 11:56

    Being able to get more granular with the feedback loop to the requestor would be a huge plus and really save my team time.

  • Kote Khutsishvili commented
    20 May 11:07

    Future consideration from 2014??

    Come on. We really need it.

  • Michelle Antici commented
    30 May 17:52

    We need to be able to map automated status updates both when we promote an idea to a feature and to a master feature. Something similar to the mapping tool when integrating with JIRA would be great. 

  • Maciej Kaminski commented
    15 Jul 12:21

    I would like to have possibility to map idea status with status of an initiative as well, customization of the mapping similar to integrations ie. AHA <-> JIRA would be powerful tool. Idea portal users would benefit from having more detail in regards to the submitted projects (if product owner would want to share that detail) + reporting on the incoming ideas would make much more sense.

  • Joe Andreana commented
    09 Aug 18:44

    This has been out here since 2014 and the requests keep on coming. Can this be prioritized to be implemented this year as it continuously gets brought up each year and gets more votes.

  • Patrick McMorran commented
    16 Sep 20:51

    +1 We want to be able to reflect what the current feature status is, so people can see if something is pending, In progress, awaiting deployment, blocked, etc.

  • Jess J commented
    02 Oct 20:22

    This would make things much easier!

    People often submit ideas to the portal that already exist as features. When this occurs I will promote those ideas to the existing feature, which links them, but it does not update the status of this idea when the feature ships like it does when promoting an idea to a new feature. This means that I need to keep track of the ideas that have linked features and manually update the status when those are finally deployed.

    It also makes it harder to scan the list to see ideas that we plan do to but have not been promoted to a feature yet vs those that have a linked feature. We will be creating a new status for ideas with linked features to help us keep track, but that doesn't alleviate the challenge of needing to do the manual status change as that idea progresses.