From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Schmitz Subject: Re: Testers / Feedback wanted: Gantt charts via org-gantt.el Date: Mon, 1 Jun 2015 12:51:50 +0000 Message-ID: <0d234207d69c4af1b0bc5048ae1fc9bf@barcarole.visus.uni-stuttgart.de> References: <1432985621669.70644@vis.uni-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43436) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YzPC9-0005tf-6s for emacs-orgmode@gnu.org; Mon, 01 Jun 2015 08:51:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YzPC5-0003eo-QK for emacs-orgmode@gnu.org; Mon, 01 Jun 2015 08:51:57 -0400 Received: from mailgw.informatik.uni-stuttgart.de ([129.69.211.41]:42093 helo=mx1.informatik.uni-stuttgart.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YzPC5-0003eW-Hr for emacs-orgmode@gnu.org; Mon, 01 Jun 2015 08:51:53 -0400 Received: from mx.visus.uni-stuttgart.de (impromptu.visus.uni-stuttgart.de [129.69.205.29]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.informatik.uni-stuttgart.de (Postfix) with ESMTPS id ADE10D43F2 for ; Mon, 1 Jun 2015 14:51:51 +0200 (CEST) In-Reply-To: Content-Language: de-DE List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org-Mode Mailing List Hi Axel, thanks for your feedback > I tried org-gantt on a current project and ran into one problem: >=20 > I track progress with > * Task [%] > and > * Task [/] >=20 > Of course the % causes a problem when exporting to LaTeX. > I suggest to either ignore [%] and [/] or use them as an alternative to s= how 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 an= y documentation - you can possibly tell I haven't been using or mode for to= o 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 featu= res. 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 th= e first > day of the chart. > (Maybe mark the task or label with a color to indicate that they are inco= mplete.) > (See below for some different ideas.) I fixed this. You can now set :incomplete-date-headlines and :no-date-headl= ines to keep, inactive or ignore. If inactive, the styles set via :inactive-bar-style and :inactive-group-sty= le are used. All options also have an org-gantt-default... defcustom, which can be set i= f you don't want to set it for each chart. =20 > A two month chart doesn't fit into \textwidth. > I wrapped it into a sideways environment (provided by rotating.sty), mayb= e a > sideways option? Hmm, I don't see an advantage of having a sideways option vs. wrapping it m= anually, but perhaps I'm missing something? I have added an option :lowlevel-scale (e.g. 0.5 or 0.75) that will scale t= he 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 exp= ort 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[=3Dname]" and add "comp= ress calendar" to the :options list to use months instead of days. Note that you should set :weekend-style and :workday-style to the same thin= g, as org-gantt will otherwise mark some months as weekends. Unfortunately, if you have sub-day effort estimates, this will currently no= t be displayed correctly, as the start and end shift is computed based on d= ays. I should probably look into that. Supporting weeks is difficult, as pgf-gantt does not natively support them = for compression, only for titlecalendar.=20 =20 > 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 deadlin= e 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? >=20 > 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 ma= in 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 tagge= d > :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 th= at, 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