Task Config only saved for last task of multi-target import

XMLWordPrintable

    • Critical
    • None
    • FIX: task-Config was not properly set for multi-target tasks
    • None

      PROBLEM

      In multi-target projects, the task-configuration (which is expected to be the configs of the selected customer of level 8 & above and the configs adjusted in the wizard) is only written for the LAST child-task. The others seem to receive only the configs adjusted in the import-wizard.
      This is a major Problem for OKAPI which expects the used OKAPI-Version to be part of the task-config - and therefore be independant from changes made in the customer or default config later on. Can there be other stuff, where this could be problematic? This e.g. will affect most of the configured services, matchrates, ...

      SOLUTION

      The config must be identical for all project-tasks

            Assignee:
            Axel Becher
            Reporter:
            Axel Becher
            None
            None
            Thomas Lauria
            Stephan Bergmann, Sylvia Schumacher
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None