[OGo-Discuss] ogo task reminder

[Adam Tauno Williams]

--=-r+DCDg9VcaKGOW+0MHl2
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > I just wonder if, for the sake of getting something sooner, if a simple=
r
> > solution wouldn't work.=20
> > In my understanding tasks have a due *DATE* and not a start *TIME* like
> > an appointment.  Would it be sufficient to simply store a "reminder"
> > property on the task, and to process the tasks for the day?  Early in
> I prefer it not to change the way how it works right now, in my eyes it i=
s=20
> the cleanest way to go.=20

Okay.

> > the day an e-mail could be sent to user(s) concerning what tasks they
> > have due in DAY + 1 (Mon - Thu) or TODAY + 3 (Fri).
> ah, yes, I see now, I removed the labels from the webui to select reminde=
r=20
> values smaller than a day ;)=20
> > Or make the property an int, number of days 1, 2, 3, or 4.  Then you'd
> > only need to scan the tasks due in the next 4 days - even at large site=
s
> > that shouldn't be more than a few hundred.
> the database field is an int, but stores the reminder value in minutes.

Right, just like the date_x reminder field.

> > In the morning the user could have an e-mail "Your due tasks" or some
> > such.=20
> yes, good idea, maybe the user should be able to configure whether he wan=
ts=20
> to have an e-mail for each due job, or a summary of all in one.
> > I do something like this with SQL, but with no OGo/WebUI integration,
> > you just get the message for all your tasks.  Just making that optional
> > would be a huge improvement.
> > > > Makes sense to me.  I'd image than the adding of the logic command =
and
> > > > the adding of the tool should be separate patches. =20
> Maybe "skyjobnotify"
> > > > should be "ogojobnotify".
> renamed it, and splitted the patch into the logic, and the ogojobnotify t=
ool=20
> including the webui patches.=20
> > That would break people's existing crontabs, etc...  so probably not.
> yeah, makes sense.
> >>>>- In the webui, a default reminder preference can be defined by the u=
ser
>> > > >in the jobs preferences page
> > > > What is the name of the default created?
> job_defnotifytime

Ok

> > > > > - maybe more...
> > > > What happens if the executant is a team?
> > > I have not tested, but I think the same will happen, as when a team i=
s=20
> > > an=20
> > > appointment participant. I only copied it from skyaptnotify.
> I checked again, and found out that teams as executants would not work at=
=20
> all. Now I changed it, to send to the team email, if set, or to resolve a=
ll=20
> team members, and send individual email to each team member.

Ok, seems reasonable.

--=-r+DCDg9VcaKGOW+0MHl2
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBF/tFkLRePpNle04MRAmQUAJ4hjLWuSlethi4wPtqgvHGHSTB8zwCfWeM0
Lh1sYSprAAZj1D2CQMAj88Y=
=AJk1
-----END PGP SIGNATURE-----

--=-r+DCDg9VcaKGOW+0MHl2--