GTG

export does not correctly make closed_date available

Bug #562604 reported by Kees Cook
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Medium
Kees Cook

Bug Description

$task.closed_date is wrong in exports. This is due to bad argument ordering in the init.

Related branches

Revision history for this message
Luca Invernizzi (invernizzi) wrote :

Awesome, thanks.

Changed in gtg:
status: New → Fix Committed
assignee: nobody → Kees Cook (kees)
importance: Undecided → Medium
milestone: none → 0.3
Kees Cook (kees)
Changed in gtg:
status: Fix Committed → Fix Released
Changed in gtg:
status: Fix Released → Fix Committed
milestone: 0.3 → 0.2.9
Izidor Matušov (izidor)
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.