emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Sven Bretfeld <sven.bretfeld@ntnu.no>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: Strategic time planing: Breaking down EFFORT property
Date: Thu, 05 Oct 2023 06:59:05 +0200	[thread overview]
Message-ID: <87o7hdk6an.fsf@web.de> (raw)
In-Reply-To: <87a5syvx0r.fsf@ntnu.no>

[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]


Sven Bretfeld <sven.bretfeld@ntnu.no> writes:

> Ihor Radchenko <yantar92@posteo.net> writes:
>> For weekly/monthly/total, you can use clock tables to summarize the time
>> spend on different projects during the week/month/in total. See
>> https://orgmode.org/manual/The-clock-table.html
>>
>> You can display additional property values in the clock table using
>> :properties attribute. That will allow seeing clocked time and your
>> estimates stored in EFFORT_* properties.
>
> I think this is what I'm looking for. I considered clock tables to be
> only for reviews, not planning. But I'm just playing with the feature
> and seem to be able to do what I want.

Can you share your setup once it is working as you want it?

What you are doing is much more complex (and useful) than what I used
EFFORT for and I would like to check whether I can adapt part of it.

I usually plan with a gantt chart in a plantuml code block:

#+begin_src plantuml :file THE-TITLE-gantt.png
@startgantt
title THE TITLE
saturday are closed
sunday are closed
2023-08-02 is closed
<style>
ganttDiagram {
  task {
    BackGroundColor GreenYellow
    LineColor Green
    unstarted {
      BackGroundColor Fuchsia
      LineColor FireBrick
    }
  }
}
</style>

' see https://plantuml.com/gantt-diagram
Project starts at 2023-09-18
[init] on {Arne:74%} lasts 2 days
[logging] on {Arne:74%} lasts 1 day
[config] on {Bera:80%} lasts 2 days
[scheduling] on {Arne:74%} lasts 1 day
[documentation] on {Arne:74%} lasts 1 day

[logging] starts at [init]'s end 
[config] starts at [init]'s end
[scheduling] starts at [logging]'s end
[documentation] starts at [scheduling]'s end

@endgantt
#+end_src

This doesn’t have the nice org-mode integration, though.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2023-10-05  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04  7:10 Strategic time planing: Breaking down EFFORT property Sven Bretfeld
2023-10-04 11:21 ` Ihor Radchenko
2023-10-04 22:28   ` Sven Bretfeld
2023-10-05  4:59     ` Dr. Arne Babenhauserheide [this message]
2023-10-05 11:53       ` Ihor Radchenko

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=87o7hdk6an.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=sven.bretfeld@ntnu.no \
    --cc=yantar92@posteo.net \
    /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).