After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 228454 - "Estimated time" property for tasks
"Estimated time" property for tasks
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Tasks
3.2.x (obsolete)
Other All
: Low enhancement
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 246569 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-08-01 15:08 UTC by jpelegri
Modified: 2021-05-19 11:44 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description jpelegri 2002-08-01 15:08:10 UTC
Package: Evolution
Priority: Wishlist
Version: 1.0.7
Synopsis: New property for tasks
Bugzilla-Product: Evolution
Bugzilla-Component: Tasks

Description:
I want a new property for tasks: «Estimated time».

In order to assign estimated time for task completion. I think it could
be useful.

Thanks.



Unknown reporter: jpelegri@gsyc.escet.urjc.es, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 André Klapper 2005-02-21 13:08:13 UTC
changing subject to a concrete one
Comment 2 Matthew Barnes 2008-03-11 00:22:02 UTC
Bumping version to a stable release.
Comment 3 Ihor Kaharlichenko 2010-06-18 13:57:15 UTC
Any updates on this issue?
If devs are too busy to take care of this issue I would like to add it myself. Just point me towards the right direction (i.e. what component/class/file should I start from?). If it could be implemented as a EPlugin it would be perfect.
Comment 4 Milan Crha 2017-01-26 16:36:05 UTC
*** Bug 246569 has been marked as a duplicate of this bug. ***
Comment 5 Milan Crha 2017-01-26 17:10:28 UTC
The only problem is that it's a non-standard property, thus an interoperability issue. See [1] what the standard properties of a task (VTODO) are.

[1] https://tools.ietf.org/html/rfc5545#page-56
Comment 6 awilliam 2017-01-27 12:32:34 UTC
As a developer of a server (CALDAV/WEBDAV) for which Evolution is used as a client... Evolution already stores lots of non-standard X- properties.  Contacts especially are loaded with them.  It is something to be concerned about - but servers are supposed to store X- properties.

Personally, I would appreciate such an attribute exposed in the UI.
Comment 7 Milan Crha 2017-02-02 08:44:22 UTC
Some servers are, some not (I think of Exchange servers here, where it is more complicated and the value is not shared between the clients other than evolution). That's semi-easily catchable by a static capability for the calendar.

I'm more concerned about the way to expose the value to the user. Should it be a free-form field, or some value with a strict formatting? The free-form means that there might not be done any calculations on it in the code.

I looked on a very old evolution (3.10.4) where an appointment editor still offers an option for the Time to be either:

   Time:  [Start date] [Start time] [for] [   0 ] hours [    30 ] minutes

or

   Time:  [Start date] [Start time] [until] [End date] [End time]

Here's that 'for' part I'm thinking of. Maybe there can be also 'days' involved, apart 'hours' and 'minutes'? I do not want to make this overcomplicated, both for the implementation and for the users.

If we figure this out by the middle of the next week, then maybe it could be part of the 3.24.
Comment 8 André Klapper 2021-05-19 11:44:38 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.