Add a new idea Subscribe
Status Future consideration
Categories Features
Created by Laura Durkheimer
Created on Mar 13, 2020

RELATED IDEAS

Configurable Default Release when creating Features from Epics/Initiatives

Currently, when creating a feature from an epic at the product line level, Aha! will look at all the products within the product line in order of when they were created, identify the first created product, and pre-select the "For release" field with the first release in that product. This is a challenge because if you have certain products that are used more widely than others, you may inadvertently create features under the incorrect product.

  • Attach files
  • Admin
    Nathaniel Collum
    Reply
    |     Mar 16, 2020

    Thanks for sharing your workflow, Laura. I see now that you're creating your features from the epics at the product line. This workflow makes sense. We'll continue to monitor feedback here.

  • Laura Durkheimer
    Reply
    |     Mar 13, 2020

    Thanks! Yes - we have the product line that is capturing our epics, and the features we're building can span across products. Therefore, we're evaluating at the epic level across teams to determine which features are needed within each product. We had to use the product line level for our epics because our product teams are on different dev cadences. Open to any other suggestions for how to solve as well! Thank you!

  • Admin
    Nathaniel Collum
    Reply
    |     Mar 13, 2020

    Thanks for sharing this idea. We'd love to better understand your use case. It sounds like you're creating features at the product line level. Is there a reason you are starting here rather than a specific product?