Add a new idea Subscribe
Status Shipped
Categories GitHub
Created by Jonathan Ross
Created on Jul 30, 2016

RELATED IDEAS

Need Aha! Requirement --> Github Issue and EXCLUDE Aha! Feature --> GitHub Issue

If you look at an Aha! Feature as a container of requirements, e.g. Aha! Feature with 3 requirements, then when you send a in the : Feature—>Issues, Requirements —> Issues; then you end up with 4 issues in GitHub - when you only need 3.

 

GitHub gets “bloated” because instead of just 3 issues showing up – it will get 4, treating the Aha! as a feature, even though development only needs to work on 3.

We do this because we go from Aha! To GitHub, and then GitHub! To Waffle.io where the Dev’s manage their Kanban board.

The Feature in the above example isn’t really supposed to be worked on as a task – it is just a container.

 

  • Attach files
  • Guest
    Reply
    |     May 4, 2017

    I just ran into this exact situation right now - it's a bit annoying to manually close/link the "container" feature.

    Alternatively, it would be nice if the "feature" issue that is the container at the very least linked to the sub-issue requirements it created!

    Even just a list of requirement issues: #1, #2, #3 on the feature issue would be nice.  As it is right now, there's absolutely no connection between them so I'm having to manually create the relationship.

    Finally, it would be nice if the Aha! id was part of the subject of the issue, IE SH-140 on the issue title, and SH-140-1 on the requirement title

  • Jonathan Ross
    Reply
    |     Jul 30, 2016

    From Aha! Support: 

    Matt was able to check in with our engineering team and we all agree that your use case makes sense. However, we currently don't enable a Requirements > Issue only mapping.

     

    From myself: =(