July 15, 2021

Issue tracking based on chain of dependencies?

Issue tracking based on chain of dependencies?

So, when developing software, it's not uncommon that in order to finish a bigger task you need to split it up into smaller tasks, and the order that you tackle these smaller tasks is dependent on each other.

For example, you can't load test a feature unless you've first implemented a feature, and you (often) can't implement a feature without describing it (in a bit more detail).

But it seems like most software is based upon describing tasks either as trees (epic -> story -> task, where each epic typically contains many stories and each story contains multiple tasks) or just a list of ordered tasks.

I know that in Jira (and some other software) you can set a task as being "blocked by" another, but the general work flow isn't really built for that. Plus Jira is overly bloated.

I'm wondering if there's any issue tracking software out there that represents tasks as chains?

As in, instead of this (typical Jira-style):

 _____________Epic____ / ___/ \__ \____________ / / \ \ Story Story Story Story | / \ | / | \ Task Task Task Task Task Task Task 

You would represent it like this:

 _________________________________________________________________ | Epic | | | | _____________ ____________ ___________________ | | | Story | | Story | | Story | | | | | | | | | | | | Task->Task |----->| Task |------>| Task->Task->Task | | | | | | | | | | | |_____________| |___________| |___________________| | | | | _____________ | | | Story | | | | | | | | Task | | | | | | | |_____________| | |_________________________________________________________________| 

(unless the project involves more than a dozen people, I personally prefer not separating into epic/story/task either, but instead just using tasks for everything – as people (including myself) can never manage to keep track of the difference between an epic, a story and a task).

The general idea would be that you hide away the not-yet-finished tasks so that you can focus on what's currently happening, so you don't clutter the board with dozens of things that will happen in the future but aren't really relevant right now.

You would also show it visually as the pyramid it really is. You could show the entire thing as a single page, where you can can click on an epic/story/task to "zoom in" to it and its nearest neighbors.

submitted by /u/Ran4
[link] [comments]