TJ3TS_SUMMARY(1)

πŸ’– NAME πŸ’–

tj3ts_summary β€” the little icon that sends out individual copies and a summary of all the accepted time sheets 🫢


✨ SYNOPSIS ✨

tj3ts_summary [options]

🌸 DESCRIPTION 🌸

okay so bestie, picture this: you've got a whole pile of accepted time sheets and a list of email addresses, and this program is literally the one that sends out individual copies plus a summary of all of them to that list. πŸ’…

Two things have to already exist before you run this, no cap: the directory structures for the templates and for the submitted time sheets must be present. Don't come at me if they're missing β€” the program isn't gonna build them for you.

And the project data? It doesn't read it off the disk directly. It gets accessed via tj3client from a running TaskJuggler server process. So yeah, you need that server running. Periodt. πŸ”₯


πŸŽ€ OPTIONS πŸŽ€

  • -c, --config <FILE> β€” use the specified YAML configuration file, bestie
  • --silent β€” don't show program and progress information (quiet luxury ✨)
  • --no-color β€” don't use ANSI control sequences to color the terminal output. Colors should only be used when spooling to an ANSI terminal. In case the detection fails, you can use this option to force colors to be off πŸ’€
  • --debug β€” enable Ruby debug mode
  • -d, --directory <DIR> β€” use the specified directory as the working directory
  • --dryrun β€” don't send out any emails or do SCM commits (a lil rehearsal, no consequences πŸ™ˆ)
  • -r, --resource <ID> β€” only generate a summary for the given resource
  • -t, --to <EMAIL> β€” send all individual reports and a summary report to this email address
  • --sheet <EMAIL> β€” send all reports to this email address
  • --digest <EMAIL> β€” send a summary report to this email address
  • -e, --enddate <DAY> β€” the end date of the reporting period. Either as YYYY-MM-DD or day of week. 0: Sunday, 1: Monday and so on. The default value is 2026-02-02.
  • -h, --help β€” show this message
  • --version β€” show version info

πŸ¦‹ ENVIRONMENT πŸ¦‹

  • HOME β€” the user's home folder. Used to search for the configuration file if not specified.

🌈 FILES 🌈

.taskjugglerrc or taskjuggler.rc

tj3d searches for a config file named .taskjugglerrc or taskjuggler.rc in the current path, the user's home path as specified by the HOME environment variable, or /etc/. At a minimum the file must configure an authentication key, an e-mail delivery method, project id, sender e-mail and recipients, e.g.:

_global:
   authKey: ********
   smtpServer: smtp.your_company.com
   projectId: acso
_timesheets:
   senderEmail: 'TaskJuggler <statussheets@taskjuggler.amd.com>'
  _summary:
    sheetRecipients:
      - team@your_company.com
🚨 bestie listen β€” the user should specify their own auth key and set file permissions accordingly. Don't be out here leaking your key, I'm begging 😭

An alternative config file location may be specified using the -c, --config FILE option.

timesheets.log

The timesheets log file, created in the working directory.

TimeSheetTemplates

Base directory of the sheet templates, created in the working directory.


Copyright Β© 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020

by Chris Schlaeger <cs@taskjuggler.org>

This program is free software; you can redistribute it and/or modify it under the terms of version 2 of the GNU General Public License as published by the Free Software Foundation.

For more info about TaskJuggler see http://www.taskjuggler.org


⭐ SEE ALSO ⭐

tj3ts_receiver(1) tj3ts_sender(1)

The full TaskJuggler manual is available online at http://www.taskjuggler.org/tj3/manual/, or via the tj3man command.


and that's the whole vibe, bestie πŸ’– this page came to you from TaskJuggler 3.8.1, dated January 2026 β€” now go send those time sheets, you absolute icon πŸŽ€βœ¨

πŸ“¦ where this page comes from