Anonymous

My feedback

  1. 111 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Anonymous commented  · 

    I think having lines could make the view quite messy (anyone that has ever used MS Project knows this can end up looking chaotic!). I think if you can intrinsically link one story as a dependency to another, then you know if the functionality hasn't been built for A then B can be displayed as 'Blocked'. If you can then see within card B which cards are blocking it then you can account for that in your prioritisation.

    Challenges I could see with this are:
    - Chain of blockages - if there was some way you could see a 'chain' of dependencies then that would be awesome, i.e. a separate view to show if ticket A is blocking ticket B is blocking ticket C, then the order of events required to release ticket C.
    - Type of dependency - is there a soft dependency on a feature being built, so you can use a copy of the feature to build similar ones? Or is there a hard dependency that a feature needs to be live in order for this new feature to function?
    - Type of card - the above sounds sensible for a story-level, but what if a story is dependent on an entire Epic being completed? Are you dependent on just the MVP being complete or every single card being complete? SOB doesn't support release categorisation to this level so currently it wouldn't know...

    Interested to see how you work this one out :)

    Anonymous supported this idea  · 

Feedback and Knowledge Base