emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Remember template with pre-defined TAGS
Date: Mon, 20 Sep 2010 15:40:25 -0500	[thread overview]
Message-ID: <AANLkTim2XBBkanOEDG8gb9Yza9beL6g4MzaAHWxLMjd=@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikXPkD880E2Q7UG_xhoTrb__pe=emtsj+Ucopyw@mail.gmail.com>

On Mon, Sep 20, 2010 at 3:35 PM, Marcelo de Moraes Serpa
<celoserpa@gmail.com> wrote:
> Hello all,
Duh, I should really try things out before asking :S

It just came to my mind that tags are, ermm, just strings, and I just did that:

     ("Bug" ?b "*** TODO %^{Description} :PROJECT_NAMEBUG:\nAdded:
%U", "~/org/gtd/gtd.org")

Simple and works like a charm!

Sorry about the stupid question. Hopefully this message archive can
teach someone else to try things out first before shooting emails.

Marcelo.

> So, my team is using onelogin in a distributed form (through git) to
> track feature (user-stories) and bugs. We track them by simple tags --
> :BUG: / :FEATURE: + A tag that specifies the project -- i.e:
>
> * TODO Fix the bug no #434 :PROJECT_NAME:BUG:
>
> It works pretty well, we have a common gtd file with all these items,
> and then just do a C-a m and search for PROJECT_NAME+BUG and there we
> get all the outstanding bugs.
>
> What I'd like to do is to allow developers to quickly input bugs, just
> like a remember template, but that include tags by default, so only
> the topic would be needed. Is it possible without too much elisp
> hacking?
>
> Thanks in advance,
>
> Marcelo.
>

  reply	other threads:[~2010-09-20 20:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 20:35 Remember template with pre-defined TAGS Marcelo de Moraes Serpa
2010-09-20 20:40 ` Marcelo de Moraes Serpa [this message]
2010-09-20 22:18   ` Sébastien Vauban

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='AANLkTim2XBBkanOEDG8gb9Yza9beL6g4MzaAHWxLMjd=@mail.gmail.com' \
    --to=celoserpa@gmail.com \
    --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).