Learning TaskJuggler 3.8.4 from scratch - created a tutorial repo

[Foad S. Farimani]

Hi everyone,

I've recently started learning TaskJuggler (v3.8.4) on Windows and wanted to share my progress. Since I found some of the existing documentation a bit fragmented between TJ2 and TJ3 syntax, I decided to document my learning path step-by-step.

I've created a GitHub repository with a series of Minimal Working Examples (MWEs) covering the basics, tracking, reporting, and even some regression testing for Ruby 3.4 compatibility issues.

You can check it out here:

https://github.com/Foadsf/TaskJuggler-Learning

The goal is to have a clean reference for setting up project management as code, specifically for newer users who might get tripped up by syntax changes (like account vs chargeset).

I would really appreciate any feedback or corrections from the experienced users here. If there are better "canonical" ways to handle things like cost accounting or scenario management in TJ3, I'd love to update my examples.

Thanks,

Foad

[Nathan Kidd]

This looks great.
My biggest hurdle with learning taskjuggler initially was understanding the relationship between durations, effort and other properties.

I ended up getting Claude to give me this list which helped quite a lot.

---

Use `effort` when:

• Writing code
• Designing features
• Writing tests
• Creating documentation
• Bug fixing (estimated work)

Use `duration` when:

• CI/CD pipelines
• Code reviews (waiting)
• Deployment windows
• Client feedback periods
• External dependencies

Use `start/end` when:

• Meetings
• Demos
• Hard deadlines
• Release dates
• Fixed time windows

Use `milestone` when:

• Release markers
• Phase completions
• Decision points
• External deliverables

---

The docs are great at explaining the fine details, but I really do think that examples is the big thing missing from taskjuggler, so I'll definitely be starring this repo.

regards
Nathan