ThinkingRock Forum

Next glitch

I create a new recurring event. I enter all the data (description, sucess) and then set the recurrence to each day derived from done date. Clicking done will regenerate the event for tomorrow as expected but the success field is empty. Maybe this has to do something with those Java errors I am constantly getting at the moment (email with log file sent to the TR crew).

I wonder If other users make the same observation

Volker

Edit:

I changed the thread subject.
See further below Claire asking for some user input

Bug. Successful outcome field was added after we finished implementing recurrency. Will add to the list for 2.0.

_________________
Claire
ThinkingRock Analyst and Tester

Claire,

I am having the same problem with the notes field. This is not carried over to the next recurrence as well.

Volker

But I am not sure the Notes should be copied across. If you recurrent action is a weekly progress meeting, notes will be different each week.

I would like to have other users opinion on this topic before designing any changes.

_________________
Claire
ThinkingRock Analyst and Tester

Claire,

for the final documentation. It may be a good idea to make clear that the notes are currently not carried over by TR design.

What I have in mind is:

I like to set up various scheduled recurring events (all day or even time specific). For example daily review events (all day) and weekly review time specific). The notes section will contain support information like trigger lists or key questions or just some instructions what to do how and why. So I'd basically use the recurrence as a kind of template. These things do not really change so the notes section seems to be an ideal place to keep this kind of information closely attached to the upcoming events.

I see your point. But If TR provides a method to make a difference between changes for the complete series of events or just the single occurence (like Outlook does) it would be no problem to enter additional and individual notes for a single occurence without carrying over those indivudal notes to the complete series. A weekly progress meeting may have a standard agenda in the "template" which can than be modified for the concrete meeting.

I like your approach of asking other users too, different views and inputs may be very helpful.

Volker

This is a tough one. I see both your points of view. On one hand it would be useful to see previous notes or have a template that can be used regularly. Saves time from retyping everything. But I also see Claire's side too.

I would hate to see such a great program like TR get bogged down by feature-itis.

Perhaps a compromise then? Either make it an option that can be enable or make it a module that can be downloaded and added later if a user wants that feature?

Just thinking outloud.

Perhaps a compromise could be reached. Each task gets its own notes field as now. But there is also a notes field on the recurring task (the window that opens when you click "Modify"). The notes field on the recurring task gets copied to each new task that's generated.

This way, we get the best of both worlds -- a template that can be generated each time (e.g. meeting structure or important info), and also each task gets its own unique notes (e.g. notes from that particular meeting).

This would be a very useful feature for me as I have tasks that have this exact structure -- some info that's the same for every recurrance, but also unique information for each generated task.

That seems good to me.