Introduct org capture template for complex tickets

From time to time, a new item introduces a more complex task that requires a
separate headline.  The new capture template is meant for this use case: it will
ask for a ticket number (the complex tasks I currently have to deal with always
come with a ticket number), a headline description, a reference (link to
redmine ticket or something), and a first task (usually a link to the first
email from the ticket).  It might be that the template is too specific, but
let's try it out first and adapt it if necessary.
This commit is contained in:
Daniel - 2020-06-21 17:03:48 +02:00
parent 72bc471f98
commit c0f7ed37bc
No known key found for this signature in database
GPG Key ID: 1C7071A75BB72D64
1 changed files with 10 additions and 1 deletions

11
init.el
View File

@ -1194,7 +1194,16 @@ in the main agenda view."
plain
(clock)
"%c"
:immediate-finish t :empty-lines 1)))
:immediate-finish t :empty-lines 1)
("T" "Record new ticket with first task"
entry
(file db/org-default-refile-file)
,(concat "* Ticket #%^{Ticket Number}: %^{Ticket Description}\n"
":PROPERTIES:\n:CREATED: %U\n:END:\n"
"\nReference: %^{Reference}\n"
"\n** %^{First Task}\n"
":PROPERTIES:\n:CREATED: %U\n:END:\n"
"\n%?"))))
:config (progn
;; disable usage of helm for `org-capture'
(with-eval-after-load 'helm-mode