Clone does not respect "Defaul Asignee" definition for a project

XMLWordPrintable

      When you clone a task, the new one is properlly located at the beginning of the workflow assigned to the project, however the asignee remains the one in the original task. If you have defined a Default Asignee in the project properties; the task should be assigned to him and is not.

      This makes the clone function completelly unusable for us; as the project lead will not be able to move the issue forward in the workflow as is not the asignee

            Assignee:
            Unassigned
            Reporter:
            Emilio Moreno
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: