From: Daniel Nemenyi <daniel@pompo.co>
To: emacs-orgmode@gnu.org
Subject: [FR] Remove blank :effort:s from taskjuggler export
Date: Fri, 03 Sep 2021 13:07:42 +0100 [thread overview]
Message-ID: <87o899n8av.fsf@pompo.co> (raw)
Dear wonderful Orgers,
Something I think would make the taskjuggler export even smoother would be if empty :effort:'s were simply skipped over, rather than exported to the tjp without a value and triggering a tj3 error. Let me explain.
Say we had the following org file, with one big feature:
---
#+COLUMNS: %70ITEM(Task) %Effort %allocate
* Big feature :taskjuggler_project:
:PROPERTIES:
:EFFORT: 4d
:ALLOCATE: alice, john
:END:
* Resources :taskjuggler_resource:
** Alice P Hacker
** John McCarthy
---
I decide that I want to break up that big task into subtasks, so I add them and switch into column view to add the efforts and allocations. Crucially, also in column view, I delete the effort estimate (using e) from the Big Feature, as otherwise taskjuggler would error that Big feature (a parent node) should not have an effort estimate when it has children.
This typical behaviour (for me) leaves me with the following.
---
#+COLUMNS: %70ITEM(Task) %Effort %allocate
* Big feature :taskjuggler_project:
:PROPERTIES:
:EFFORT: # Note empty :effort:
:END:
** Design feature
:PROPERTIES:
:EFFORT: 1d
:ALLOCATE: alice
:END:
** Code feature
:PROPERTIES:
:EFFORT: 2d
:ALLOCATE: john
:END:
** Test feature
:PROPERTIES:
:EFFORT: 1d
:ALLOCATE: alice
:END:
* Resources :taskjuggler_resource:
** Alice P Hacker
** John McCarthy
---
Alas the empty :effort: node causes tj3 to fail with a cryptic 'Error: Unexpected token 'task' found. Expecting one of :INTEGER, :FLOAT', as the effort key is exported to the tjp file without a value:
---
task big "Big feature" {
effort
task design "Design feature" {
...
---
My solution would be for org-taskjuggler-export to simply skip over empty effort symbols. Another solution might be for column view to remove symbols that have been deleted - however this might have unintended consequences?
Thanks for taking this into account, and for the amazing tool that is org mode!
Daniel
reply other threads:[~2021-09-03 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o899n8av.fsf@pompo.co \
--to=daniel@pompo.co \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.