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 136946 - WBS (Work Breakdown Structure) required ideally with custom formatting.
WBS (Work Breakdown Structure) required ideally with custom formatting.
Status: RESOLVED FIXED
Product: planner
Classification: Other
Component: General
unspecified
Other Linux
: Normal enhancement
: 0.13
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2004-03-12 00:24 UTC by Lincoln Phipps
Modified: 2005-02-18 16:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lincoln Phipps 2004-03-12 00:24:11 UTC
A WBS is a handy field because some other project tools have it and thus
people get used to using it. Also some project processes use this with
their own formating i.e. not just 1,

1.1,
1.1.1
etc
but Team A - Project 1 - Summary 1 - Task 1.

Its not actually hard to create a WBS given that the mrp_get_task position
returns the position with this depth so its simply a matter of walking back
up the heirachy to get a numerical WBS.

I suggest that we calculate a WBS field and then cast this via a printf
style  derived ideally from a Project Custom Property e.g.
WBSPREAMBLE = ""
WBSFIELDDELIMITER = " - "
WBSDEPTH1SUBSTITUTE = "A,B,C,D,E,F,G,I,J,K,?"
WBSDEPTH1FORMAT = "Group %c"
WBSDEPTH2FORMAT = "Project %d"
WBSDEPTH3FORMAT = "Summary %d"
WBSDEPTH4FORMAT = "Task %d"
WBSPOSTAMBLE = "."

This can then be used in the Task View printouts and export to HTML etc as
well as in the Task Dialog. Given its derived data there probably is NOT a
need to actually add it to the database/DTD schema, though I think it would
be helpfull as its complex for 3rd party things to calculate this.

Well thats my thoughts anyway.
Comment 1 Richard Hult 2004-03-25 23:50:54 UTC
I've commited code that hardcodes this to 1.1.1, etc. I don't think we should
add formatting and a UI for that unless we really know it's needed.

Adding support for it in the storages might be a good idea.
Comment 2 Lincoln Phipps 2004-03-25 23:55:14 UTC
I can look at what you've done and I can add the storage stuff.
I think its neccesary to store it in SQL/XML/HTML  etc as it'll
be nice for post-processing/reporting systems.
Comment 3 Richard Hult 2005-02-18 16:25:02 UTC
I'm not sure it's useful to save this data, it's really just a property of the
ordering of the tasks in the UI, at least with the current implementation. I'm
closing this bug, and we can add another one if needed.