emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Grouping clock report by tag?
Date: Thu, 24 Feb 2011 18:25:10 -0600	[thread overview]
Message-ID: <AANLkTikKAAnMBPiNP0CA0zDgVMMPjz9qE1t267-5AjV_@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 2053 bytes --]


I just decided to try to start clocking tasks and would find it most helpful
to organize by tag, not file. Perhaps my filing system is unorthodox, but I
originally started using an org file per work project but just found it
cumbersome when it came to recording my notes since I'd be switching back
and forth between many files. I suppose I could have used capture for this,
but I think my current system makes more sense. It is to use one file per
month and the format is like so:

| ~/org/2011-02Feb.org
| ---
| * [2011-02-04 Fri]...
| * [2011-02-08 Tue]...
| * [2011-02-22 Tue]...
| ** Description of something I did          :project-name:
| CLOCK: [whatever]--[whatever]
| Notes
| ** Something else I did this day            :other-project:
| CLOCK: [whatever]--[whatever]
| Notes

Hopefully that's clear. I like this method as it keeps file sizes down and
just seems more organized than how I was before.

In any case, I realize that I can setup clock reports with something like
=:tags "project-name"= to get a report for a particular tag. That can at
least give me per-project reports for a given timeframe, but I wouldn't mind
the ability to have something that shows all my time but includes tags

Perhaps it would display the headline (which is actually nice since my top
headlines are the dates), then the sub-item (which would be helpful because
it would be a description of what I was doing), but somehow give a summary
of time-per-tag or a column that lists the tag for teach task as well? Is
this possible? That would be great as I'd be able to get a snapshot of how I
spent my day per project.

Again.. manually, this is possible as I can create a "clockreport.org" file
with a headline per project with a specific =:tag "project-name"= argument
and then I could add up times and compare them from there. Though perhaps
there's a better way to get something like this as well?

Thanks for any thoughts or even sharing how you use clocking when it comes
to analyzing the data afterward.

Best regards,

[-- Attachment #1.2: Type: text/html, Size: 2584 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

             reply	other threads:[~2011-02-25  0:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  0:25 John Hendy [this message]
2011-03-06 13:20 ` Grouping clock report by tag? Bastien
2011-03-06 17:02   ` John Hendy
2011-03-06 17:42     ` Bastien
     [not found]       ` <AANLkTim6kxpDVxXw5krSbpDK+x3=wfB2iqN6g9nWujx2@mail.gmail.com>
2011-03-06 18:08         ` John Hendy
2011-03-07 10:11           ` Giovanni Ridolfi
2011-03-11 22:06             ` John Hendy
2011-05-05 19:33               ` [Orgmode] " John Hendy
2011-05-05 23:08                 ` Bernt Hansen
2011-05-06 20:30                   ` John Hendy
2011-05-06 23:55                     ` Bernt Hansen

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:

  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=AANLkTikKAAnMBPiNP0CA0zDgVMMPjz9qE1t267-5AjV_@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).