[Tickets #13886] old task completion status needs migration, new entries miss data

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/13886
------------------------------------------------------------------------------
  Ticket           | 13886
  Erstellt Von     | jmozdzen at nde.ag
  Zusammenfassung  | old task completion status needs migration, new entries
                   | miss data
  Warteschlange    | Nag
  Version          | 4.2.4
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


jmozdzen at nde.ag (2015-02-27 11:54) hat geschrieben:

For some releases now (cannot tell since when - about 2 months, I  
guess), my existing tasks are not recognized as "completed", and thus  
are displayed even when selecting to display only pending tasks.

All those tasks do show the "completed" checkmark as "checked".

We're using the Kolab backend to store the task data.

When completing new events, this feature works.

Comparing an old and a new completed task in the IMAP store, I see the  
following difference:

--- cut here: old entry ---
   <completed>100</completed>
   <status>not-started</status>
   <due-date>2010-01-15T10:00:00Z</due-date>
   <completed_date>2010-01-19T16:07:48Z</completed_date>
--- cut here ---

--- cut here: new entry ---
=20=20<priority>3</priority>
=20=20<completed>100</completed>
=20=20<status>completed</status>
=20=20<due-date>2015-02-27T01:00:00Z</due-date>
--- cut here ---

So the old entry has, for whatever reason, a status of "not started",  
but does have a "completed_date". Sounds weird, but worked with older  
version of Horde.

The new entry has no "completed_date" (which sounds like an error to  
me - missing information!), but a status of "completed".

 From the user interface, both events look alike, but filtering the  
view seems to have changed to work on "status" now (which seems like a  
proper decision, of course).

I see the following two problems:

1. How can we mass-migrated the status of old tasks to "completed" for  
all those entries that have a "completed_date" set?

2. No longer having the "completed_date" in new entries seems like a  
bug to me.