Existing Event can be "Hidden" when adding new events
Bug #1350605 reported by
Jason
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Calendar App |
Fix Released
|
High
|
Jason |
Bug Description
The Calendar App "drops" an existing event when adding a new event. The "dropped" event disappears from the DayView for the current run of the app, but "re-appears" after closing and re-opening the app. So no data is lost permanently, the problem *appears* to be limited to the display alone.
Reproduction Steps
1) Start the calendar app
2) Create a new event "Foo"
3) Create a second event "Bar"
4) After creating the second event, check the DayView, the "Foo" should no longer appear.
I'm not sure when this issue was initially introduced, but it was noticed around 7/30/14 when it started causing Jenkins builds of the calendar app to fail.
Related branches
lp:~gerlowskija/ubuntu-calendar-app/fix-for-bug1350605
- Nicholas Skaggs (community): Approve
- Kunal Parmar: Approve (code review)
- Ubuntu Phone Apps Jenkins Bot: Approve (continuous-integration)
- Kill Animals (community): Approve
- Mihir Soni: Approve
-
Diff: 125 lines (+42/-25)2 files modifiedTimeLineBase.qml (+33/-5)
tests/autopilot/calendar_app/tests/test_new_event.py (+9/-20)
Changed in ubuntu-calendar-app: | |
status: | New → Confirmed |
Changed in ubuntu-calendar-app: | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Changed in ubuntu-calendar-app: | |
status: | Triaged → In Progress |
milestone: | none → rtm14 |
Changed in ubuntu-calendar-app: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I have not tried to reproduce the issue, but if you are able to reproduce can you put log when we get model refresh event and see how many events are returned by model.
If you are getting correct number of events from model then we need to investigate from calendar side.
else we need to check EDS side.