Add Features to multiple initiatives

Many intiatives may benefit from some common functionality.   If you could add a feature to multiple initiatives it would allow you to better track the impact of the feature across the entire business.

  • Bob Carlson
  • Mar 20 2015
  • Will not implement
Release time frame
  • Dec 12, 2018

    Admin Response

    We appreciate the feedback on this idea. Despite the interest in this request, we do not plan to implement this idea.

    That said, please note that there are a couple workarounds which would allow you to link a feature to multiple initiatives and understand the impact of the features across the business.

    1. Add an initiatives record relationship custom field to capture secondary initiatives for a feature

    2. Use record links to connect the feature to secondary initiatives

    While we can see value in particular cases for directly linking a feature to multiple initiatives, allowing this would cause other issues and limitations that may not be apparent on the surface. Since initiatives typically represent a large body of work, it is important as that work is broken down into features to be able to clearly delineate which features contribute to the work of the initiative. 

    For example, we have a major effort underway to provide enhanced capacity planning capabilities which will allow you to manage estimates and capacity at the initiative level for high level planning (which can be tracked in this idea.) This would not be possible if a feature could be related to more than one initiative.

    Implementing this would also limit future improvements to roadmap visualizations where you may want to see your initiatives and features in a single roadmap.

    Given the available workarounds and limitations of introducing this capability, we hope you can understand why we do not have plans to implement this idea.

  • Attach files
  • Scott Shultz commented
    4 Feb 01:48pm

    It is very limiting for a feature or master feature to link to only one initiative. In the real world it is very normal for features to be linked to multiple initiatives, as evidenced by the number of comments in this thread. Adding an additional custom field doesn't solve the problem. Please fix this limitation. 

  • Josh Tambor commented
    15 Jan 07:51pm

    Following on this thread...it would be helpful to get some additional beyond the above Admin response. I will say that adding a custom field is a good work around, however, it may become a large burden for an admin to manage a large amount of fields in time. With respect to the link feature, I do not think this a strong feature in its current state. It is a bit limiting in respect to how it is viewed. Given that the response was issued in Q4 2018, and that Aha has made some strategic choices around its position as an end-to-end management tool for strategy and requirements (i.e. inclusion of new workspace types), any additional guidance from the team is greatly appreciated

  • Loic Bauduin Brunelle commented
    26 Aug, 2019 11:20am

    The problem is about reporting, this could still be solved without breaking the future development.

    What about including the "record links" concept in the reporting structure, so that we can pull related object data using the record links instead (or in addition to) the object hardcoded links?

  • Loic Bauduin Brunelle commented
    26 Aug, 2019 11:16am

    The problem is to report a feature against multiple large initiatives.

    This idea refers one solution for this problem, which is to link a feature to multiple initiatives through the feature->initiative attribute. Understanding that this would break your solution, could you still provide a solution to the original problem "out of the box" / without requiring use of custom fields?

    What about including the "record links" concept into your reporting solution?

  • Yogev Barom commented
    20 Feb, 2019 02:08pm

    Thank you

  • Zachary Levin commented
    18 Dec, 2018 01:50am

    This feature would really help us deal with a strategy aiming to integrate disparate product lines through multiple initiatives and consequently have major benefits to our prioritization system - identifying features tied to multiple key strategic initiatives

  • Ben Hampton commented
    12 Dec, 2018 04:54pm

    Thanks for the explanation!  Knowing this won't be implemented helps clarify how we should be best representing the initiative object.

  • Harrison Lynch commented
    12 Dec, 2018 03:41pm

    In retrospect, only a madman would want this feature. 😀

    (But you were very kind in your explanation)

  • Johan Criel commented
    20 Nov, 2018 11:27pm

    Idea++.

    Any feedback from Aha! side regarding this topic?

  • K W commented
    11 Oct, 2018 03:10am

    We're a Fortune 100 and love using Aha. This feature is important to us; any progress on this?

  • Walter Clarke commented
    3 Oct, 2018 12:41pm

    Please let us know when this will be available or not; either way we need to know. It will impact our use of the Aha! tool moving forward

  • Zach Robin commented
    2 Oct, 2018 09:06pm

    Lack of this feature is limiting further expansion of Aha! within our global organization. 

     

  • Jerrold Emery commented
    5 Sep, 2018 04:44pm

    Are there any updates on this request? It certainly has a lot of votes and plenty of comments. It would be nice to see this item move forward.

  • Greg Koeka commented
    27 Jul, 2018 02:59pm

    This would benefit one of our primary Product tasks, stakeholder communication. When leadership wants to know how a feature helps us achieve our initiatives, and thus our goals, we can't show them the value of the team's efforts. This is fundamental for both a Product manager and the team.

  • Annette Edmonds commented
    25 Jul, 2018 09:10pm

    Prior to entering an enhancement request I noticed there are many asking for the same option which is to allow linking a feature to "multiple" initiatives.  I agree that there are many times that it would help prioritize, understand the where initiatives cross, etc.

  • Guest commented
    25 Jul, 2018 04:38pm

    I very much agree with this! Has there been a decision? Seems like this has been "future consideration" for a long, long time.

  • Chris Garner commented
    5 Jul, 2018 09:31pm

    I wish John Biltcliffe would have shared his work around.  We desperately need this

  • Ken Cantu commented
    2 Mar, 2018 03:45pm

    We have multiple initiatives at the corporate level and some features we're delivering span those initiatives even if they are secondary benefits. From the initiative level we have higher decision maker users who want to see a few of an initiative and all the features that help support and move that initiative forward in reporting. 

  • Shawn Adams commented
    19 Jan, 2018 07:10pm

    This would help sell to senior leadership the desire to work on something by being able to show that working on one Idea or Feature is addressing multiple initiatives at the same time.  Senior leadership loves to know when something is killing two birds with one stone.

  • Johny Wudel commented
    29 Nov, 2017 11:36pm

    For us an initiative is a specific area of focus that will help us reach a goal. For example, "create frictionless onboarding for customers" is an initiative. And then also "reduce calls to support" is another one. We could have a feature that we want to associate with both initiatives. 

    You can do this on a release. We'd like it on the feature as well.

  • Load older comments
  • and 85 more