Starting with version 0.9.7, Flyspray can have tasks that depend upon other tasks. Basically what this means is that if task #1 depends upon task #2, you cannot close #1 until #2 is closed. The image below shows the dependencies block.

On the left you can see the tasks that this task depends upon. The line through some tasks indicates that they have been closed. The tasks without a line through them are stopping this task from being closed. In fact, the button to close a task will not even appear until all dependencies are closed. Simply close all the tasks that this task depends upon, and you can then close this task.

Beneath the dependencies is a small text field and a button that let you add another dependency to this task. Simply enter the task id in the text field, and click the “Add new” button. Note: Flyspray will not let you create a dependency back to the same task, nor can you create a dependency of a task that this task is blocking. If you did that, you would never be able to close some tasks! If you receive an error when you try and add a dependency, this is probably why.

On the right of the picture, you can see a list of tasks that depend upon this task. In other words, this task blocks some other tasks from closing. You must close this task before you can close other tasks that depend upon it.

To add or remove dependencies, you need to have permission to edit the current task. This means that you need to meet one of the following two criteria:

• If the task is assigned to you, be a member of a group with the Modify Own Tasks permission, or
  
• Be a member of a group with the Modify Other Tasks permission.
  

Since the 0.9.8 release (or develoment versions after August 10, 2005), Flyspray has a feature that allows it to draw a pretty picture that shows the relationships between your tasks that have dependencies. As of the 0.9.8 release, it still requires an extra software package to be installed (the “dot” tool from the free Graphviz package) in order to function. Enhancements are in progress 612 to remove this limitation, and allow it to generate the image remotely rather than on the local machine. If you're interested in using this feature, but it isn't working properly, see the Installation page for more information.