Community
Participate
Working Groups
Quite often I have things I want checked weekly, be it a status call or checking some logs The context menu to schedule a task lists 7 days ahead, but it would eliminate a few clicks in a couple of cases would it have 8 days ahead. Not sure if that's deemed to specialized or not though :)
Have you tried Schedule for > Next Week?
But that schedules it for the week, right? The intention is to still be able to get it scheduled for a specific date, not a full week range.
Right, the current scheduling mechanism does not have automation for recurring tasks. I know we have had some discussions around that in the past but can't currently find the corresponding task. I think it's an important feature that we should consider for an upcoming release.
Big +1. I've come to rely heavily on the "Scheduled" View in the Task list and use it to plan my day, everything from development tasks to "get milk". I have a few tasks I need to at the start and end of every day, and I rely on my calendar to keep me informed. It'd be fantastic to see them in the task list, since, however, since I'm in there already. It's much easier to see "what I haven't done yet" in the task list than it is to look at my Calendar for the same information, since a calendar has no notion of "Completed"
(In reply to comment #4) > Big +1. I've come to rely heavily on the "Scheduled" View in the Task list and > use it to plan my day, everything from development tasks to "get milk". > > I have a few tasks I need to at the start and end of every day, and I rely on my > calendar to keep me informed. It'd be fantastic to see them in the task list, > since, however, since I'm in there already. It's much easier to see "what I > haven't done yet" in the task list than it is to look at my Calendar for the > same information, since a calendar has no notion of "Completed" +1
If I'm reading correctly there seem to be a couple suggestions here: - Add another day (or two) to the "Scheduled" drop-down. For example I can select today (Wednesday) through next Tuesday, it would be nice to (re-)schedule something for next Wednesday without the popup. - Recurring tasks - scheduling a task for every (nth) week - status call, tag the sprint, etc. For me the first would be nice, the second could be really great, especially with an end date.
I think I would want to have tasks automatically appear under furture dates, but I would want them to remain scheduled for the current date until I indicate somehow that I've completed this instance of the task. If I had a task scheduled for the 1st of every month, I might not get to it until the 2nd, and I wouldn't want it to have it disappear from my task list until I've actually done it.
Created attachment 226230 [details] mockup Here's a simple proposal for how this should work: * scheduled dates should not be changed automatically * the schedule for menu should have an option to configure a recurring schedule which would allow the user to specify that the task recurs every N days/weeks/months * once the user has configured the recurring schedule, the schedule for menu should have another option to schedule the task for the next recurring date. This would be the *only* effect of having a recurring schedule configured. * We could consider a prompt if the user explicitly sets a task to not scheduled, asking if they want to reschedule it for the next recurring date Let's say a task is scheduled for the 1st of each month. On the 1st, the user would see the task scheduled for today and could reschedule it as they desire (for later in the week, say) without affecting the recurring schedule. Once they have completed this iteration of the task, they would change the scheduled date to the next date in the recurring schedule. This avoids adding any potentially confusing behaviour that would automatically change the scheduled date of a task. It also makes sense for both local and repository tasks.
Does anyone have any thoughts on the proposal in comment 8? It would be great to get some basic support for this in Mylyn. We could add an end date to the recurring schedule if that would be useful. The main thing I see missing from this is that there would be no indication when you have completed an iteration of the task, but that seems more like a nice-to-have feature than something essential.
I am concerned that it will be hard to discover/understand that logic, and the whole thing around the recurring day not getting affected by reschudelung the current instance might just confuse people a lot. I wonder if for starters this can be simplyfied by just a few more options. One more day (instead of 7) to allow "same day next week", and maybe a "same day(week) next month" option could help many cases without being complex.
I like Thomas' idea as it's straightforward and apparently makes the bug reporter happy ;) Another approach could be modifying the context menu to look like this: For a scheduled task: Tuesday Wednesday ... Monday --- This Week Next Week Two Weeks --- Repeat > Every Week > Every Two Weeks > Every Month --- ^^^ single choice Choose Date Not Scheduled For a not scheduled task: ... Two Weeks --- Repeat > Every Monday > Every Tuesday > Every ... > Every Sunday --- ^^^ multiple choice ... Recurring task stops once completed.
(In reply to comment #11) > Recurring task stops once completed. +1 to Tomasz's approach on the context menu, but I think tasks should still be recurring even though it can be marked as completed (for this instance of task) until user explicitly make the task not recur anymore. When you change the scheduled date for a recurring task, a pop up box should come up asking if the change will be made only on this instance of task or on all future recurring tasks. Same thing would occur if the task becomes unscheduled.
Thanks for the feedback. I'd prefer to solve the general (and common) case of arbitrary recurring schedules rather than only supporting one more day. Here's an updated proposal for how this should work: * The schedule for menu should allow users to configure a recurring schedule. What exactly the UI looks like is not important right now. * Once the user has configured the recurring schedule, the schedule for menu should have another option to "complete" this instance of the task and reschedule it for the next recurring date (the task would not actually be marked as completed). This would be the *only* effect of having a recurring schedule configured. * We could consider a prompt if the user changes the scheduled date, asking if they want to reschedule only this instance or update/cancel the recurring schedule. This is not much different in function than my earlier proposal, but it may be easier for users to understand. I can't see a good way to show that an instance of a recurring task is complete, and I'm not convinced there is much value in that, but we could consider adding support for that later.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
