[Tickets #14197] Re: Nag_Driver_Kolab stores parent_id strings base64 encoded (should be: unencoded)

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14197
------------------------------------------------------------------------------
  Ticket             | 14197
  Updated By         | mike.gabriel at das-netzwerkteam.de
  Summary            | Nag_Driver_Kolab stores parent_id strings base64
                     | encoded (should be: unencoded)
  Queue              | Kolab
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


mike.gabriel at das-netzwerkteam.de (2015-12-29 17:45) wrote:

> Either way, we can't use the internal ID of the task as the parent  
> property. It MUST be the UID. If the regex isn't enough to catch the  
> incorrectly set properties, maybe we can perform a look up of the  
> UID to ensure it exists? That would be alot more expensive, so if we  
> do need to do that, maybe we'd have to move this to a login task  
> after all...

Looking up the UID is not needed and not useful, I guess.

Please note that when looking at all tasks (complete and  
non-completed), parenting of tasks should always work (unless a parent  
task got removed).

But when looking at e.g. completed tasks, the parenting is broken  
anyway, because often sub-tasks are marked as completed whereas parent  
tasks are still set to not-completed.

If the parent UID lacks from the list of tasks to be shown, the  
sub-task is simply shown at top level. I would not put too much effort  
into solving this.

/me wonders how other groupware / tasklist tools handle that  
(parenting of completed and non-completed) tasks.