A tracker artifact should be able to block more than one other artifact.
This would be useful for handling bugs and tasks.

Comments

  • Can you please elaborate and provide some business use cases driving this enhancement request?

  • Sometimes a issue may not be resolved until another issue (e.g. in a used library) has been resolved.

    Perhaps it is better to use a new relationship ("blocked by"-"blocking") for this and leave the parent-child relationship unchanged.

    This approach could be used to prevent configurable state transitions of the blocked artifact (e.g. to "resolved" or "in review").