Hi, Olivier. Based on a couple of years of watching the forums here is what I have concluded:
MLO staff read many but not all new posts (as opposed to comments on existing posts). If they see a new post and it’s a bug report they will respond with support (but sending bug reports to the support email address is a little more likely to get a response) If they see a new post and it describes an enhancement that they find appealing, likely to increase user satisfaction and/or revenue, not likely to be hated by very many users, easy to understand, not that expensive to build and consistent with the founder’s vision of how the product may evolve, they may engage with the request. Once this happens there’s a good chance that the MLO staff will engage with the discussion around the suggestion. Olivier, you have pulled this off several times. If there is a post with a slightly less appealing enhancement request (eg popular but controversial) I believe that there’s a good chance that they will notice it but a lesser chance that they will engage with the discussion. In almost all cases (except the rare post that draws MLO staff into the discussion) I believe that MLO staff are highly unlikely to notice the comments and comments offering “+1” or “metoo” have little influence on the future of the app. As I have mentioned previously I think that uservoice requests that make it to the top ten, or the first page or whatever get serious consideration. MLO staff may not be implementing it but they will at least figure out why not, and might tell you if you ask. I say this fully aware that uservoice tends to promote old requests above new ones, that people who post suggestions without checking for similar existing recommendations split the vote and reduce the idea’s chances, and that there is no active curator combining similar requests or removing ones whose time has passed. -Dwight From: [email protected] [mailto:[email protected]] On Behalf Of robisme (Olivier R) Sent: Saturday, April 05, 2014 3:41 AM To: [email protected] Subject: Re: [MLO] Re: Same Task in Two Locations Thank you for this information. For my part however, There are some features I had requested on this google groups that have been released. (eg : new smart-filter ctrl+L, auto-jump to first tab if double click a task, ability to see the tasks linked to one task...) I didn't put those requests on the user voice, but here, so I think they also look at this forum, don't they ? Perhaps the uservoice shoud have tags or even #tags ? Olivier Le vendredi 4 avril 2014 16:08:55 UTC+2, Dwight Arthur a écrit : Hi, Olivier. It is true that there are a number of unresolved issues with UserVoice and the one you cite is an important one. There is nobody in charge of consolidating requests. I for one would not want that job because in some cases the requests are similar but have areas of difference over which people disagree. The best suggestion is to use the comments area for each request to ask potential voters to support one or the other of the proposals in order to have more impact. This is not a great solution but I have seen it work. I should mention that I have definitely seen MLO development priorities be influenced by uservoice voting in some cases. I am pretty sure that supportive comments to forum posts have little to no chance of affecting developer priorities. For the record, there is another channel named JIRA that seems even more effective but access is limited to users who have volunteered and been accepted to the beta testing program. -Dwight From: [email protected] <javascript:> [mailto:[email protected] <javascript:> ] On Behalf Of robisme (Olivier R) Sent: Friday, April 04, 2014 9:23 AM To: [email protected] <javascript:> Cc: [email protected] <javascript:> ; [email protected] <javascript:> ; Barbara Mettler Subject: Re: [MLO] Re: Same Task in Two Locations Dwight, Is there someone in charge of gather similar requests? I mean, very often, there are request that are formulated differently but are, indeed, the same need. (It can be an old request). The problem is that it underestimates the number of votes. For this reason, I don't use the MLO voic anymore. Olivier Le vendredi 4 avril 2014 13:09:31 UTC+2, Dwight Arthur a écrit : Hi, Stephen. I just wanted to point out that nobody tracks how many comments in this forum say that they are voting for some enhancement. If you want to vote and have it count you should use http://mlo.uservoice.com -Dwight Mlo betazoid on Android sgn2 On Apr 3, 2014, ssintay <[email protected]> wrote: I just wanted to add my vote for this capability to be added in the future. On Saturday, January 19, 2013 11:38:30 AM UTC-7, Brad Konia wrote: I agree with the previous postings requesting logical linking functionality within MLO. I've also used Ultra Recall and I find their logical linking implementation to be nearly perfect, as well as extremely simple. This feature would not require any changes to the hierarchical structure, nor would it introduce any added complexity. You would simply be creating aliases or pointers to specific branches in the hierarchy, at other locations in the hierarchy. This would be analogous to a symbolic link within a Linux file system, which is also hierarchical. Implementing this functionality would make it much easier to create task hierarchies without having to stress over where to place each task, when it could logically be placed in more than one location within the hierarchy. I realize you can get much of this functionality using contexts. The problem is, the MLO user interface is designed primarily around the task hierarchy, not contexts. I tried using a flat task list and organizing everything by context and it didn't work out. The context editor allows you to include contexts within other contexts, but there's no way to build an inclusion hierarchy. It just allows you to enter a list if contexts that are included within another context. Additionally, when you add a new task, the context selector displays every context you've created in one long list, rather than allowing you to select contexts hierarchically. If you try to use contexts as your primary organizational strategy within MLO, you'll end up with a big mess that will ultimately be too cumbersome to use efficiently. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <javascript:> . To post to this group, send email to [email protected] <javascript:> . Visit this group at http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/f2dae4e0-0265-414e-9a52-abad4693bbca%40googlegroups.com <https://groups.google.com/d/msgid/mylifeorganized/f2dae4e0-0265-414e-9a52-abad4693bbca%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/a612a203-4d69-464d-88ed-5ade943ee614%40googlegroups.com <https://groups.google.com/d/msgid/mylifeorganized/a612a203-4d69-464d-88ed-5ade943ee614%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/001801cf536b%2499590d70%24cc0b2850%24%40dwightarthur.us. For more options, visit https://groups.google.com/d/optout.
