Wrong default in item dependency dialog

XMLWordPrintable

    • Type: Incident report
    • Resolution: Incomplete
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      When adding a trigger dependency, the selection dialog defaults to first template in first template group, instead of the template i'm actually working on. Wouldn't the latter be more useful?

            Assignee:
            Unassigned
            Reporter:
            Tony den Haan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: