| 2010-05-03 14:55:24 |
Gediminas Paulauskas |
description |
This bug depends on # 532428 however I think it should be a part of # 532428.
bug # 532428 described a feature allowing sections to have its own time boundary. this bug requests the time boundary should be able to change. if the user changes the time boundary of a section, the journal should be updated to reflect the change (preferrabely ask user before if some journal information fell out of the boundary thus might be dropped), and related calendar events should be created.
Note this is related to #559403 "allow not only deleting but also adding event to a section", because if #559403 can be done, it offers a way to extend the section by creating new events after the section end time. |
This bug depends on bug #532428 however I think it should be a part of it.
Bug #532428 described a feature allowing sections to have its own time boundary. this bug requests the time boundary should be able to change. if the user changes the time boundary of a section, the journal should be updated to reflect the change (preferrabely ask user before if some journal information fell out of the boundary thus might be dropped), and related calendar events should be created.
Note this is related to bug #559403 "allow not only deleting but also adding event to a section", because if that can be done, it offers a way to extend the section by creating new events after the section end time.
|
|
