When promoting idea to feature allow automatically pass the idea category to a feature custom field.

Currently it passes info only from idea custom field to feature custom field. I want to leverage the already existing idea categories to pass them as product components/areas into feature and then again into Jira ... all in sync. I have the workaround off course to manualy duplicate the categories in a custom field, or manually re-enter them when promoting to Jira ... but would be useful for all this to be streamed lined...

  • Aristotel Dascal
  • Dec 11 2015
  • Unlikely to implement
Release time frame
  • Attach files
  • Admin
    Ron Yang commented
    December 11, 2015 18:28

    As you described, we do currently have the ability to pass information from an Idea custom field to a feature custom field. We do also have the ability to sync feature custom fields in Aha! to Jira custom fields. The best way to support your use case would be through this workflow.

    While we realize that this may require you to duplicate the categories into a custom field, the end goal can still be achieved.

    Given this workaround, general feedback from the overall community, we're unlikely to make changes in this area in the near-term.

  • Christopher Anderson commented
    March 27, 2017 10:40

    Added my vote. My objections with custom fields are the same - duplication.

  • Paulo Branco commented
    July 11, 2017 14:47

    Ron, the workaround is not a good solution. The idea custom field is not displayed in the ideas portal. I agree with this idea, if you want to avoid double data-entry the category should be automatically copied over to features. If  you want to go a step further, this should also be sent to jIRA.

    thanks

    Paulo

  • Claire Matt commented
    August 01, 2018 14:49

    We really struggle with this.  For us, to take full advantage of promoting ideas to features, we should be able to carry over those fields without double entry.  Please reconsider!!

  • Guest commented
    October 11, 2018 18:36

    Categories are valuable in Features, too! It seems silly to have to replicate a built-in field with a custom one. Also, if we use a custom field in the Idea, will that allow the nice list on the left side in the Ideas portal?

  • Laura Giles commented
    22 Feb 08:25

    Manual duplication & mgmt of datasets is bad practice and shouldn't be a requirement for 'automation' ESPECIALLY when we don't even have the ability to bulk manage categories (aka undue burden / terrible admin ux), copy categories to other products, easily manage categories like custom fields nor select a custom field as a portal category filter, etc..

    Aha support docs recommend using categories as an identifier for x-portfolio idea submission scenarios but doesn't deem it important enough to carry over to the feature?? Why even have an alternate identifier dataset that cannot be used? PMs don't want to have to flip back and forth between ideas & features/initiative to reference user-defined data that should have pulled through. (bad PM ux) 😭(also noting that Aha baseline feature status (i.e. 'will not do' & 'already exists') also do not auto sync to baseline idea status)

    Aha's heavily touted ability to automatically sync feedback to features was why we as a company considered adopting Aha globally in the first place but appears to have been a platform after thought and we have solved nothing that a much cheaper spreadsheet couldn't handle.

    Hopefully Aha plans to invest in the feedback<>feature sync process near term as well as correct all the category design issues.