rtm plugin does not support fuzzy dates
Bug #492775 reported by
Luca Invernizzi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GTG |
Fix Released
|
Medium
|
Luca Invernizzi | ||
Bug Description
and I have no idea how to add that at the moment. Ideas, anyone?
Related branches
Revision history for this message
| Luca Invernizzi (invernizzi) wrote | #1 |
| Changed in gtg: | |
| importance: | Undecided → Medium |
| Changed in gtg: | |
| assignee: | nobody → Luca Invernizzi (invernizzi) |
| status: | New → Confirmed |
| milestone: | none → 0.3 |
| status: | Confirmed → New |
| Changed in gtg: | |
| status: | New → In Progress |
| Changed in gtg: | |
| status: | In Progress → Fix Committed |
| Changed in gtg: | |
| milestone: | 0.3 → 0.2.2 |
| Changed in gtg: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Up to now, the fuzzy date is maintained in gtg, while on rtm it remains blank.
If the rtm task is changed, that prevails and therefore the FuzzyDate becomes a NoDate.
I think that preserving the fuzzy date in this case is incorrect, as it breaks the "whichever is newer wins" rule.