From: Bernhard Schmitz <Bernhard.Schmitz@vis.uni-stuttgart.de>
To: Org-Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Testers / Feedback wanted: Gantt charts via org-gantt.el
Date: Mon, 1 Jun 2015 12:51:50 +0000 [thread overview]
Message-ID: <0d234207d69c4af1b0bc5048ae1fc9bf@barcarole.visus.uni-stuttgart.de> (raw)
In-Reply-To: <A8E885FC-3E83-43AE-B21B-2EADD602DCC1@axelkielhorn.de>
Hi Axel,
thanks for your feedback
> I tried org-gantt on a current project and ran into one problem:
>
> I track progress with
> * Task [%]
> and
> * Task [/]
>
> Of course the % causes a problem when exporting to LaTeX.
> I suggest to either ignore [%] and [/] or use them as an alternative to show how
> much is completed.
> It is probably a better metric than hours worked.
I do not quite understand: Is this an org mode feature (I could not find any documentation - you can possibly tell I haven't been using or mode for too long), or is this just something that you do yourself?
While I agree that it would be a good idea to use those numbers, I'm a bit wary of implementing something that is not based on official org mode features.
As a preliminary measure, I now ignore % signs.
> pgfgantt doesn't handle \ganttbar commands without start and end date.
> Therefor I can't export an incomplete chart.
> You may want to set the entries with missing scheduling information to the first
> day of the chart.
> (Maybe mark the task or label with a color to indicate that they are incomplete.)
> (See below for some different ideas.)
I fixed this. You can now set :incomplete-date-headlines and :no-date-headlines to keep, inactive or ignore.
If inactive, the styles set via :inactive-bar-style and :inactive-group-style are used.
All options also have an org-gantt-default... defcustom, which can be set if you don't want to set it for each chart.
> A two month chart doesn't fit into \textwidth.
> I wrapped it into a sideways environment (provided by rotating.sty), maybe a
> sideways option?
Hmm, I don't see an advantage of having a sideways option vs. wrapping it manually, but perhaps I'm missing something?
I have added an option :lowlevel-scale (e.g. 0.5 or 0.75) that will scale the complete resulting chart.
You can of course also use the pgfgantt options (:options) x unit chart and y unit chart for more specific scaling.
> For a project with 2000 person hours[1] I'll probably need a separate export and
> print it on A0 paper[2].
> Some kind of scaling would be fine (show weeks / month instead of days).
You can already set :title-calendar to "year, month[=name]" and add "compress calendar" to the :options list to use months instead of days.
Note that you should set :weekend-style and :workday-style to the same thing, as org-gantt will otherwise mark some months as weekends.
Unfortunately, if you have sub-day effort estimates, this will currently not be displayed correctly, as the start and end shift is computed based on days. I should probably look into that.
Supporting weeks is difficult, as pgf-gantt does not natively support them for compression, only for titlecalendar.
> For a huge project it may be nice to limit the levels printed:
> Just Module 1 - 8 for the Management and each Module with the submodules for
> the project leader.
> Similar to maxlevel in the clocktable.
I added an option :maxlevel (and org-gantt-default-maxlevel)
> I'm not sure about inheritance:
> If I have a deadline for a task, should the subtasks inherit that deadline unless an
> explicit deadline is given?
> If I have a deadline for a task and efforts for all subtasks, should the task inherit
> that effort?
>
> That way I can give a deadline to the task and estimate efforts to get an initial
> chart.
> Using this chart I can divide the subtasks between workers, rearrange the
> deadlines for the subtasks and finally define a scheduled date for the main task.
This works for ordered subheadlines. Deadlines are propagated downwards, if the subheadlines are ordered.
If the subheadlines are not ordered, deadlines are only propagated upwards, as it is not clear which task(s) should inherit the deadline.
So you can set a deadline to the (last) subtask, and it will be propagated to its supertask.
> This gives me another idea:
> Filter / color by tag.
> Print only tasks tagged :Axel: to show my workload, and print tasks tagged
> :Sam_One: to show tasks I have delegated.
Isn't this already doable by using sparse trees? Or would this involve some unnecessary hassle? I'm not an experienced enough org user to determine that, but I don't want to replicate functionality that already exists.
> Color tasks by tags to show who is assigned, white for unassigned tasks.
Noted for future support.
Regards,
Bernhard
next prev parent reply other threads:[~2015-06-01 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 11:33 Testers / Feedback wanted: Gantt charts via org-gantt.el Bernhard Schmitz
2015-05-31 13:13 ` Axel Kielhorn
2015-06-01 12:51 ` Bernhard Schmitz [this message]
2015-06-01 15:26 ` Axel Kielhorn
2015-06-01 18:38 ` Axel Kielhorn
2015-06-02 8:42 ` Bernhard Schmitz
2015-06-01 11:16 ` Karl Voit
2015-06-02 8:15 ` Bernhard Schmitz
2015-06-03 15:13 ` Karl Voit
2015-06-02 8:38 ` Eric S Fraga
2015-06-03 15:17 ` Karl Voit
2015-06-05 8:20 ` Bernhard Schmitz
2015-06-20 12:46 ` Bernhard Schmitz
2015-06-25 8:04 ` Eric S Fraga
2015-11-09 15:02 ` Karl Voit
2015-08-05 0:00 ` Bastien Guerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d234207d69c4af1b0bc5048ae1fc9bf@barcarole.visus.uni-stuttgart.de \
--to=bernhard.schmitz@vis.uni-stuttgart.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).