Calendar date-times incoherences when DST occurs on 27th March
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Bill Filler | ||
Ubuntu Calendar App |
Fix Released
|
High
|
Renato Araujo Oliveira Filho | ||
qtpim-opensource-src (Ubuntu) |
Fix Committed
|
High
|
Renato Araujo Oliveira Filho |
Bug Description
I'd rather to create another bug-id even if the Bug #1562891 seems
similar at first sight (Time-date & Calendar issue UTC/Local),
but I've noticed an issue about times displayed in Calendar-app:
the time is incoherent between the displays.
BUG DESCRIPTION :
When DST changed from UTC+1 to UTC+2 , the times displayed
for an events serie is not coherent, like it is shown in the joined
screenshots numbered from 1 to 5. You can realize:
1- The DST changed from UTC+1 to UTC+2 (Europe/Paris),
and 'Set the time and date' is Automatically.
2- This screenshot show that now the event has changed
to 13:00 - 13:05 . Originally it was set at 12:00 - 12:05
3- This window shows that the event (dated 30 March)
can be modified but it is set at 13:00 - 13:05
4- Now I edit this event with the funtion 'Edit series'...
5- The page shown, now displays the 9th March
at 12:00 - 12:05. Which is incoherent.
WHAT THE LAST WINDOW SHOULD DISPLAY :
1- A page with a date of 30 March with a time 12:00 - 12:05.
2 -if I edit any event starting from the 27th March,
all the notifications should display 12:00 - 12:05
because originally it was set at this time.
3- If I edit an event, say the 30th March and I
decide to change it to 12:30 - 12:35 , all
occurring serie from 30th March should
be modified from 30th March.
And as well, all occurring serie before 30th March
should be unchanged.
CONCLUSION:
The user should not have to change the time set even when
the DST occurred. An event set to 12:00 before a DST
should remain to 12:00 after a DST.
Related branches
- Arthur Mello (community): Approve
- Jenkins Bot: Approve (continuous-integration)
-
Diff: 103 lines (+66/-1)3 files modifiedcalendar_canvas.js (+7/-0)
click/calendar.apparmor (+3/-0)
tests/unittests/tst_calendar_canvas.qml (+56/-1)
- PS Jenkins bot: Approve (continuous-integration)
- Ubuntu Phablet Team: Pending requested
-
Diff: 37 lines (+10/-9)1 file modifiedorganizer/qorganizer-eds-engine.cpp (+10/-9)
Changed in canonical-devices-system-image: | |
assignee: | nobody → Bill Filler (bfiller) |
Changed in canonical-devices-system-image: | |
milestone: | none → 11 |
Changed in ubuntu-calendar-app: | |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
importance: | Undecided → High |
Changed in ubuntu-calendar-app: | |
assignee: | nobody → Renato Araujo Oliveira Filho (renatofilho) |
milestone: | none → 0.6 |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
Changed in ubuntu-calendar-app: | |
status: | New → Won't Fix |
Changed in ubuntu-calendar-app: | |
status: | Confirmed → In Progress |
Changed in qtpim-opensource-src (Ubuntu): | |
status: | New → Confirmed |
assignee: | nobody → Renato Araujo Oliveira Filho (renatofilho) |
status: | Confirmed → In Progress |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
tags: | added: system-apps-11 |
Changed in ubuntu-calendar-app: | |
status: | Fix Committed → Fix Released |
Changed in qtpim-opensource-src (Ubuntu): | |
status: | In Progress → Fix Committed |
importance: | Undecided → High |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
May I ask the meaning of "Won't fix", does that mean it will never be fixed forever ?
An explanation is welcomed for a new bug reported. Thanks.