Skip to Main Content
Status Unlikely to implement
Categories Product
Created by John Hopkin
Created on Sep 24, 2015

Link a Feature to multiple products

We regularly release features across Desktop, Web and Mobile which we have as separate products in aha. We would prefer to be able to have a feature which is linked across all products, as all are updated at the same time. We currently add features per product but there is no central link back to a single feature. 

  • ADMIN RESPONSE
    Jul 22, 2022

    Currently, features can only be linked to a single product.

    This is done in an effort to simplify the number of products used within Aha! Depending on your release cycles, it may be more beneficial to set up your product hierarchy to have 1 product and use tags to identify the environment.

    Please see more details here: https://www.aha.io/support/roadmaps/strategic-roadmaps/workspaces/define-product-workspace

    At this time, we do not have plans to link features across multiple products. We hope you can understand.

  • Attach files
  • Guest
    Jun 4, 2020

    this would be useful for me as well. i have an internal-facing project, but i do need to "mirror" select/specific features to the client-facing projects for the items that impact them.

  • Adam Czubak
    May 22, 2019

    Agree that this would be excellent feature.  We build enterprise level software with many Modules that are separate product lines. There are dependencies for some customers across the product lines.

  • Admin
    Austin Merritt
    May 21, 2019

    Hi there. Features only belong to a single product in Aha! There are a couple options for handling situations where a feature may be related to more than one product:

    1. Use a master feature with individual features in each product
    2. Add a Product custom field to your features layout to capture secondary product relationships. When adding the custom field, choose the Product type field in the Aha! record relationships section. This field will then be pre-populated with the products from your product hierarchy.

    The current model of a feature belonging to a single product is not something that we are likely to change. I hope you can understand and find the options above helpful. Thanks!

  • Guest
    May 20, 2019

    Does linking of feature with different product is still NOT supportable in Aha!?

    Please reply!

  • Rachel Patterson
    Apr 27, 2018

    It looks like you can now use master features in one product and link features to them from other products. 

  • Guest
    Apr 5, 2018

    I think this is big miss here to. This starts to make features limited to something similar to a task rather than a feature.

  • Guest
    Feb 2, 2018

    Totally agree with Marissa too! Big miss not supporting a feature for multiple products.

  • Chris Martin
    Jan 12, 2018

    Late to this idea, but wanted to note that it's also becoming more common for individual features to be "packageable" into various product offerings. It would make sense to be able to track/release a single feature in Aha and have the roadmaps of all products leveraging feature reflect when that feature has shipped.

  • Chiara McPhee
    Apr 21, 2017

    Agree with Marissa completely.

  • Marissa Melnick
    Feb 8, 2016

    I think this is a big miss.  Similar features are often released across multiple products (web, mobile, etc), with different release cycles, so it would seem that this use case should be pretty common.  The suggested alternative does not seem to be a viable solution.

12 MERGED

I'd like the ability to alias a feature into another product

Merged
I'd like the ability to have a feature card appear in multiple products, currently I find myself duplicating a feature and moving it to another product because of a dependency or to have the feature mirrored in different products/product lines. Ho...
Jesse Stein over 5 years ago in Features 0 Unlikely to implement
13 MERGED

Assign a feature to multiple products

Merged
I have a feature in a current gen product that I also need in a next gen product. I don't want to create the feature and all its associated information multiple times. I have this feature mapped to a release in the current gen and now I want to ma...
Guest over 6 years ago in Product 1 Unlikely to implement