Tickets :: [#13360] Adding a tasks list in Nag makes it the default

6.0.0-beta1

7/18/25

Summary	Adding a tasks list in Nag makes it the default
Queue	Nag
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	software-horde (at) interfasys (dot) ch
Created	07/13/2014 (4023 days ago)
Due
Updated	07/28/2014 (4008 days ago)
Assigned	07/28/2014 (4008 days ago)
Resolved	07/28/2014 (4008 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/28/2014 05:52:32 PM	Michael Rubinsky	Comment #7 Taken from Horde Developers State ⇒ Resolved	Reply to this comment
Turns out we already were doing that, but only the Kolab driver was marking the 'default' flag in the share. Fixed.

07/28/2014 05:50:19 PM	Git Commit	Comment #6	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_2): commit 951f60727216d3ec75be707a4cdbe7a53506bc1f Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Mon Jul 28 13:44:34 2014 -0400 This share parameter isn't specific to Kolab. Correctly fixes ~~Bug: 13360~~ nag/lib/Tasklists/Base.php \| 2 ++ nag/lib/Tasklists/Kolab.php \| 9 --------- 2 files changed, 2 insertions(+), 9 deletions(-) http://github.com/horde/horde/commit/951f60727216d3ec75be707a4cdbe7a53506bc1f

07/28/2014 05:45:50 PM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git (master): commit 16e3c86c473ff8da4c0e3fbe9f7470b7db72f7f7 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Mon Jul 28 13:44:34 2014 -0400 This share parameter isn't specific to Kolab. Correctly fixes ~~Bug: 13360~~ nag/lib/Tasklists/Base.php \| 2 ++ nag/lib/Tasklists/Kolab.php \| 9 --------- 2 files changed, 2 insertions(+), 9 deletions(-) http://github.com/horde/horde/commit/16e3c86c473ff8da4c0e3fbe9f7470b7db72f7f7

07/28/2014 05:11:20 PM	Jan Schneider	Comment #4 State ⇒ Assigned Assigned to Horde Developers	Reply to this comment
We may want to store the default notepad though if one cannot be retrieved from prefs, but is determined automatically. IIRC that's how we do it in Kronolith.

07/20/2014 07:05:51 PM	software-horde (at) interfasys (dot) ch	Comment #3	Reply to this comment
Actually, this is working as expected. This is happening because a default tasklist has not been explicitly selected. In this case, the first tasklist in the list (the most recently created one) is used as default. Once one is explicitly selected (and saved) in the prefs, this behavior will stop. OK. I guess the user realises quite quickly when adding tasks that the newly added list has become the default and will check the preferences if he wants to make some changes.

07/20/2014 06:57:37 PM	Michael Rubinsky	Comment #2 State ⇒ Not A Bug	Reply to this comment
Actually, this is working as expected. This is happening because a default tasklist has not been explicitly selected. In this case, the first tasklist in the list (the most recently created one) is used as default. Once one is explicitly selected (and saved) in the prefs, this behavior will stop.

07/14/2014 03:31:17 AM	Michael Rubinsky	Assigned to Michael Rubinsky State ⇒ Assigned

07/13/2014 05:53:39 PM	software-horde (at) interfasys (dot) ch	Comment #1 State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Nag Summary ⇒ Adding a tasks list in Nag makes it the default Type ⇒ Bug Priority ⇒ 1. Low	Reply to this comment
This seems like a bug to me as I don't understand the rationale for making the latest added list the default one.