Creating tasks in a user's task list not belonging to an execution breaks the console. For example:

Task task = taskService.createTask();
task.setName("name ..");
task.setAssignee("assignee ..");
taskService.save(task);

After the creation the jbpm-console breaks and can't display tasks of this user anymore. An exception is then thrown telling that the executionId is null. I consider this a bug since there can be tasks not belonging to an execution. I verified that this is an issue with the console or the console integration. Retrieving the user's task list via the API afterwards works fine and shows all tasks regardless if they are belonging to an execution or not.

Could anybody verify if this bug persists in the console distributed with jBPM 4.2?