Recurring tasks

Hi Babynus,

we have several tasks which have to be performed on a regular basis.

As is: I have to enter or to copy this tasks for every periode I would like to put it on task list.

To be: For Tickets, Actions and may be Activities, it should be possible to set up recurrent. Setting the events on done, it should create a new one, based on rules like every month or every Tuesday. It should have a deadline, until this recurrance should take place - e.g. ten times or until end of a year.

Example: If a recurring Ticket is done / closed, then it should make a copy with a new due date according given rules and creation date is day of copying. Responsible might be copyied automatically.

Regards,

Klaus

Hi climb4fun

Very good idea

cordially

Hi all!

A "possible improvement to this already planned improvement":

Many of these recurrent tasks are of those kind that people usually don't really like doing, such as "take out the garbage", "check our vehicule's health", "verify all the fire-extinguishers' expiration date"

So, one idea could be to define a set of several responsible people, and on each iteration assign the newly created task on "the next one". To "share the load", sort of speak

I.e.: I define a new recurrent task "take out the garbage", and assign PETER, LOLA and JOHN as reponsibles. So, Projeqtor automatically creates the first task (with deadline e.g. within a week) and assigns PETER as reponsible. The week passes by, Peter takes out the garbage, and closes the task. So, Projeqtor "knows" it needs to create a new "Take out the garbage task", with deadline set a week from then, BUT now it assigns Lola as reponsible. Obviously, third time it would assign John, and then restart the cycle.

I hope it's clear what I meant.

---

EDIT

---

Now, one more thing I'm not so sure how to deal with.

Let's suppose I define 10 recurrent, not-liked weekly tasks. And assign my three previously introduced resources (Peter, Lola and John) as responsible for all of them. If I create the list of "responsibles" the same way in every recurrent task (i.e.: 1-Peter, 2-Lola, 3-John), Projeqtor would, on the first week, assign ALL 10 recurrent tasks to Peter, the 2nd week all 10 recurrent tasks to Lola, and the 3rd week all 10 recurrent tasks to John.
We'd have one extremely frustrated and irritated resource per week, and that's not good for us, is it?

So, one thing Projeqtor could do in order to help us, would be to "randomize" (of course, on choice) the list for every activity, so as to distribute more evenly, and based "purely" on luck.

Of course, this could be done "by hand" (reordering the list on every activity) but I'm thinking of Projeqtor "Managing teams" in the hopefully-not-so-distant future