From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Kyle Farrell <kaf@nwlink.com>
Cc: emacs-orgmode@gnu.org, Marcelo de Moraes Serpa <celoserpa@gmail.com>
Subject: Re: export weekly completed/late items
Date: Wed, 09 Feb 2011 09:36:07 -0600 [thread overview]
Message-ID: <87fwrxqkyg.fsf@dustycloud.org> (raw)
In-Reply-To: <19793.39409.384877.468341@bitter.patentinvestor.com> (Kyle Farrell's message of "Tue, 8 Feb 2011 11:30:57 -0800")
I do this for generating work reports, but all I do is
#+begin_src emacs-lisp
(setq org-log-done 'time)
(setq org-log-state-notes-into-drawer t)
#+end_src
To enable logging (second line is to prevent cluttering things up)
Then in the agenda:
press "v l" to enable logging
press "v a" to enable archived trees
press "b" to go back a week.
It also helps that I have
#+begin_src emacs-lisp
; Start weekly view from present day
(setq org-agenda-start-on-weekday nil)
#+end_src
set so that the agenda starts on the current day.
I usually end up generating reports for the last two weeks... I've
considered looking to see if there's a way to set up agenda commands to
generate a list of the last two weeks' tasks so I didn't have to press
back twice, but I haven't tried yet :)
Does that help?
- cwebb
Kyle Farrell <kaf@nwlink.com> writes:
> I'm a bit of a newbie to org-mode, so where should I start to look at
> this? Is there existing functionality in either org-agenda or
> org-export that would be a good starting point?
>
>
> Marcelo de Moraes Serpa wrote:
>> This is a great idea, and one I would use myself. I don't think you
>> could configure the agenda to build something like that though, I'd
>> say we'd need to come up with some custom elisp code or a script that
>> parses the org archive file and does the dirty job.
>>
>> Marcelo.
>>
>> On Mon, Feb 7, 2011 at 2:04 PM, Kyle Farrell <kaf@nwlink.com> wrote:
>> > I'm trying to create a weekly report of items completed or
>> > outstanding. I'd like to bucket these by status. I've got my entries
>> > with a DEADLINE calendar date set.
>> >
>> > For example given the org input:
>> >
>> > * TODO Fix bug for software project X
>> > DEADLINE: <2011-02-07 Mon>
>> > * DONE Update documentation for feature Y
>> > DEADLINE: <2011-02-09 Wed>
>> > * DONE Scope out new version of Z
>> > DEADLINE: <2011-02-09 Wed>
>> > * TODO Code new version of Z
>> > DEADLINE: <2011-02-17 Thu>
>> >
>> > I'd like to bucketize these based on the current date TODO status. If
>> > the date is 2/11/2011, based on the deadline and the status I'd like
>> > to see:
>> >
>> > Missed:
>> > 2011-02-07: Fix bug for software project X
>> >
>> > Completed:
>> > 2011-02-09: Update documentation for feature Y
>> > 2011-02-09: Scope out new version of Z
>> >
>> > Coming up:
>> > 2011-02-17: Code new version of Z
>> >
>> >
>> > Am I best using an agenda view to create this? Or would this be in a
>> > custom exporter?
>> >
>> > thanks!
>> > -Kyle
>> >
>> > _______________________________________________
>> > Emacs-orgmode mailing list
>> > Please use `Reply All' to send replies to the list.
>> > Emacs-orgmode@gnu.org
>> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>> >
>>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
--
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
next prev parent reply other threads:[~2011-02-09 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 20:04 export weekly completed/late items Kyle Farrell
2011-02-08 18:14 ` Marcelo de Moraes Serpa
2011-02-08 19:30 ` Kyle Farrell
2011-02-09 15:36 ` Christopher Allan Webber [this message]
2011-02-09 16:41 ` Marcelo de Moraes Serpa
2011-02-09 16:52 ` Bastien
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=87fwrxqkyg.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kaf@nwlink.com \
/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).