Are there any plans to introduce issue dependency at all? This is helpful
when there are different development teams involved.
As an example, say Issue #1 has two separate parts, one is an API being
implemented by team #1 and the other is using that API to implement the
actual issue. Issue #2 is dependent on Issue #1 being completed first. This
is also helpful in tracking actual time/money for an issue that can be
spread over different teams.
John De Lello
DelWare Software Solutions, LLC
"Risk everything, or gain nothing"
-Geoffrey De Charny