Problem with tasks created in public/shared folders



  • Hallo.

    i have same problem on 3 different kopano servers,

    1. create task in any public or shared from other account tasks folder and assign this task to another testuser.
    2. task appears in public/shared folder.
    3. testuser getting email with new task.
    4. testusers accepting task.
    5. Test user can see this task in 2 places: testusers own tasks folder and in shared/public folder.
    6. testuser can edit,close and do what he should do with task in testuser own task folder and he can’t do anything with same task in public/shared folder.
    7. changes that testuser makes in task in testuser own task fodler not displayed in same task in public/shared folder.
    8. sender can’t see any changes too.
    9. in public/shared folder from any side. task has status “Waiting for response from recipient”

  • Kopano

    Task in public folder is currently not supported.

    For me sending, accepting shared task works fine.
    If you assign a task to another user [user2] this user becomes the owner of the task.

    If you edit the task inside a shared store, make sure you have delegate permissions to send items on behalf of.
    If not, the mail will bounce.



  • For me sending, accepting shared task works fine.

    I have 2 servers in production and 1 for test (fresh install ) . All servers installed as Univention App.
    I can’t work with tasks in shared folders.

    If you assign a task to another user [user2] this user becomes the owner of the task.

    User becomes task, but this task exists in 2 places:

    1. user task -(user can edit etc
    2. same task in shared folder - user can’t edit and task has status “Waiting for response from recipient”
    3. Sender can see only task in shared folder with status “Waiting for response from recipient”

    And now for example user finished task in own task folder, but sender don’t know about it, because sender can see only tesl in shared folder with status “Waiting for response from recipient”


Log in to reply