Skip to Main Content
Status Future consideration
Categories Reports
Created by Nick Mariette
Created on Jul 31, 2017

Represent Master Features in all releases where there is an associated Feature

When a Master Feature that has several Features spans more than one release, I want to be able to see the Master Feature represented on all releases where a Feature is defined not just the Release in which is completed.

  • Attach files
  • Melissa Robbins
    Reply
    |
    Jan 21, 2020

    This seems like others that are sitting out there. I submitted an idea as well. Could all of these ideas be merged?

    • A-I-8671 
  • Guest
    Reply
    |
    May 10, 2019

    I have exactly the same issue.

    I would need a Master feature to show up in every release where one of the features linked to the master feature is shipped.

  • Nick Mariette
    Reply
    |
    Aug 10, 2017

    Here is some more output from the example built using an Aha trial account (same one as used in earlier comments). Here's a screenshot (Fig. 1) of a report where I have several master features across several releases, with some master features that span epics across different releases. In the live report output, I can see the master features, and I have de-selected the epics. In the report export (Fig. 2), those master features that were linked to an epic, but not the release (e.g. mf1 in release 1) do not appear any more. I can see how this might be intended behaviour, however it is frustrating and not what I would like. I would like to see which master features are being addressed in any given release, even if I've de-selected the epics (because I might have a long detailed list of epics). I also do not want to use the master feature report because it also does not include master features if they are attached to epics but not attached to the release itself (Fig. 3).  I hope this explains my issue. 

  • Nick Mariette
    Reply
    |
    Aug 10, 2017

    Hi Austin,

    Thanks for checking. It turns out that I had unselected the epics that relate to the master feature on the particular release that then did not show the master feature in the export. If I reselect those epics, I can once again see the master feature in the export. What's strange is that the master feature shows in the report, but not the exported version. I would like to not have to show the epics in order to see the master feature. I hope this extra information enables you replicate this issue and see what I mean. 

  • Admin
    Austin Merritt
    Reply
    |
    Aug 9, 2017

    Hi Nick, I am not able to replicate the issue you are experiencing. My hunch is that there is an issue with the master features you have created or the filters on your roadmap. Can you double check that the filters aren't set in a way that they would be filtered out? Also, if you are still having issues, could you respond to support@aha.io with more detail? That way our Customer Success team can help you get this cleared up. You can reference this idea. Thanks!

  • Nick Mariette
    Reply
    |
    Jul 31, 2017

    Hopefully the final comment for today:

    I don't know if it is relevant, but if I select the "master features" tab instead of "features" in the top right corner of the Features Report page, then I get an empty page, no matter how many check-boxes I select. I start with a Features Report that is showing data, for which there are existing master features. I select master features, and then I get absolutely no data showing. When I tested the same thing in the Fredwin demo, I was able to get a visible report (see attached).

  • Nick Mariette
    Reply
    |
    Jul 31, 2017

    See "ease of use" master feature on the "test" release in the image above.

  • Nick Mariette
    Reply
    |
    Jul 31, 2017

    As more information, I am trying to export a report that looks almost identical to the report in the last image on this page:

    https://support.aha.io/hc/en-us/articles/115001477463-Master-features-overview

    Where for example, the master feature "partner inventory management" appears on the first three releases. This works in the display in Aha, but when I go to export an image, only one of the releases will have the master feature. 

    Strangely, I tried starting a trial of Aha from here: https://support.aha.io/hc/en-us/articles/115001477463-Master-features-overview

    and did the minimal number of steps to try and replicate the problem there, however it all worked properly there! (see attached image)

  • Nick Mariette
    Reply
    |
    Jul 31, 2017

    On this related idea https://big.ideas.aha.io/ideas/APP-I-4821, Austin Merritt notes: 

    "Master features can span multiple releases. In your example, you could create a single Integrations master feature and place it in the 3.2 release which is where you would anticipate it will have been fully developed. You will deliver it incrementally over the three releases, so the features in those individual releases can all be linked to the same master feature. If you display it on your Features roadmap, the icon for the Integrations master feature will show up across all three releases."

    Unfortunately the bold text above is only true when you view the report directly in Aha. When you try to export an image of the report it is not true. The master feature then only shows up on the release where the master feature is originally placed (on the features board/master feature view).

1 MERGED

Allow a Master Feature to span multiple releases

Merged
Today I have no way to create one master feature and have it span across multiple releases. I either resort to duplicating the Master Feature and/or moving it after a release is done. I need a way for a Master Feature to represent work being start...
Melissa Robbins about 4 years ago in Epic 0 Future consideration