dependencies between tickets

[anonymous]

It would be nice to build workflows with the ticket system. Let me create an example:

You have 1 mainfeature, 3 subfeatures, 1 task and 3 tests. Now you can build the following with the ticket system:

mainfeature A —> subfeature 1 —> test 1

—> subfeature 2 —> test 2 —> subfeature 3 —> task 1 → test 3

Now it is possible to see which requirements or features depends on other requirements/features. This can be useful if you want to divide a general feature into several subfeatures. Or you can create a task to show that there is something to do to implement a requirement/feature. On the other hand it is possible to restrict the possibilities for tickets if they have dependencies. So it would be possible to close subfeature 1 only if test 1 is already closed (successful test).

[Emmanuel Blot]

Duplicate of many other requests about ticket relationship: #31, #886 for example.