![]() ![]() links below jump to the message on this page. Thread overview: (only message) (download: mbox.gz / follow: Atom feed) Thanks for taking this into account, and for the amazing tool that is org mode! Another solution might be for column view to remove symbols that have been deleted - however this might have unintended consequences? My solution would be for org-taskjuggler-export to simply skip over empty effort symbols. Expecting one of :INTEGER, :FLOAT', as the effort key is exported to the tjp file without a value: This typical behaviour (for me) leaves me with the following.Īlas the empty :effort: node causes tj3 to fail with a cryptic 'Error: Unexpected token 'task' found. 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. 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. #+COLUMNS: %70ITEM(Task) %Effort %allocate Say we had the following org file, with one big feature: 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. Remove blank :effort:s from taskjuggler export archives help / color / mirror / code / Atom feed * Remove blank :effort:s from taskjuggler export 12:07 Daniel Nemenyi 0 siblings, 0 replies only message in threadįrom: Daniel Nemenyi 12:07 UTC ( / raw)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |