Dependencies

When working on a complex piece of software like a game, it’s quite common to have many interconnected systems and features that often depend on each other. Managing those dependencies properly avoiding bottlenecks and blockers can be tricky. In order to help you with that matter, we provide a task dependency system that allows you to define which tasks depend on each other and block them until their dependencies are resolved. Blocked tasks are marked with a lock watermark and colored in a darker tone, and they can be edited but can’t be moved to another stage.

You can set dependencies from the task editor, clicking on a task card on the kanban board or game design model section. Go to the lock icon tab and click on the plus icon button. This launches a dialog where you can search for tasks by ID or title and select one or more of them. When the dependencies are added they are evaluated and the current task is blocked if the conditions are met.

The purpose of the dependencies feature is letting you know if a task can be started or not, so when one task is blocked the system is constantly checking for its dependencies. When all the blocking dependencies of a task are resolved (moved to the Completed stage), the task will be automatically unblocked. Alternatively, if a dependency was completed but moved back to one of the previous stages, the task will be blocked again.

Note: HacknPlan provides notifications to inform you when a task has been blocked or unblocked, which is critical for the team to know when they can start working on it. The notifications can be configured by individual users from their settings and select between UI and email notifications. Premium users can also get these notifications in Slack.

 

hacknplan

This entry has 0 replies

Comments are closed.