home.social

#timetrackingsoftware — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #timetrackingsoftware, aggregated by home.social.

  1. After many years, there's finally a new KTimeTracker release!

    It has been ported to Qt6 and should be arriving to distributions eventually, and at some point, Windows. A flatpak is also underway, but you can already try the nightly if you're feeling curious (currently no difference from the release).

    rabbitictranslator.com/ktimetr

    #KDE #Linux #KTimeTracker #TimeTracking #TimeTrackingSoftware #Flatpak

  2. After many years, there's finally a new KTimeTracker release!

    It has been ported to Qt6 and should be arriving to distributions eventually, and at some point, Windows. A flatpak is also underway, but you can already try the nightly if you're feeling curious (currently no difference from the release).

    rabbitictranslator.com/ktimetr

    #KDE #Linux #KTimeTracker #TimeTracking #TimeTrackingSoftware #Flatpak

  3. After many years, there's finally a new KTimeTracker release!

    It has been ported to Qt6 and should be arriving to distributions eventually, and at some point, Windows. A flatpak is also underway, but you can already try the nightly if you're feeling curious (currently no difference from the release).

    rabbitictranslator.com/ktimetr

    #KDE #Linux #KTimeTracker #TimeTracking #TimeTrackingSoftware #Flatpak

  4. Software zur Zeiterfassung gesucht. Soll als Lehrer meine Zusatzaufgaben dokumentieren, für Verfügungsstunden. Gerne für #linux, #windows, #android. Jeder Tipp ist willkommen. #zeiterfassung #timetracking #timetrackingsoftware

  5. Software zur Zeiterfassung gesucht. Soll als Lehrer meine Zusatzaufgaben dokumentieren, für Verfügungsstunden. Gerne für #linux, #windows, #android. Jeder Tipp ist willkommen. #zeiterfassung #timetracking #timetrackingsoftware

  6. Software zur Zeiterfassung gesucht. Soll als Lehrer meine Zusatzaufgaben dokumentieren, für Verfügungsstunden. Gerne für #linux, #windows, #android. Jeder Tipp ist willkommen. #zeiterfassung #timetracking #timetrackingsoftware

  7. Software zur Zeiterfassung gesucht. Soll als Lehrer meine Zusatzaufgaben dokumentieren, für Verfügungsstunden. Gerne für #linux, #windows, #android. Jeder Tipp ist willkommen. #zeiterfassung #timetracking #timetrackingsoftware

  8. Software zur Zeiterfassung gesucht. Soll als Lehrer meine Zusatzaufgaben dokumentieren, für Verfügungsstunden. Gerne für #linux, #windows, #android. Jeder Tipp ist willkommen. #zeiterfassung #timetracking #timetrackingsoftware

  9. In conclusion though, clearly I'm using the p: tag as a workaround; semantically it's part of the primary category, eg the “config file” project is always a subcategory of fos.hledger work, never of per.fin work. So it would be cleaner in some sense if account name checking was a little more flexible and I could keep subdividing the account name.

    6/

    #hledger #plaintextaccounting #timetrackingsoftware

  10. In conclusion though, clearly I'm using the p: tag as a workaround; semantically it's part of the primary category, eg the “config file” project is always a subcategory of fos.hledger work, never of per.fin work. So it would be cleaner in some sense if account name checking was a little more flexible and I could keep subdividing the account name.

    6/

  11. In conclusion though, clearly I'm using the p: tag as a workaround; semantically it's part of the primary category, eg the “config file” project is always a subcategory of fos.hledger work, never of per.fin work. So it would be cleaner in some sense if account name checking was a little more flexible and I could keep subdividing the account name.

    6/

    #hledger #plaintextaccounting #timetrackingsoftware

  12. In conclusion though, clearly I'm using the p: tag as a workaround; semantically it's part of the primary category, eg the “config file” project is always a subcategory of fos.hledger work, never of per.fin work. So it would be cleaner in some sense if account name checking was a little more flexible and I could keep subdividing the account name.

    6/

    #hledger #plaintextaccounting #timetrackingsoftware

  13. In conclusion though, clearly I'm using the p: tag as a workaround; semantically it's part of the primary category, eg the “config file” project is always a subcategory of fos.hledger work, never of per.fin work. So it would be cleaner in some sense if account name checking was a little more flexible and I could keep subdividing the account name.

    6/

    #hledger #plaintextaccounting #timetrackingsoftware

  14. Sample reports:

    $ hledger bal -DN --pivot=acct:p

    || 2024-06-18
    =========================++============
    biz:res: || 0.50
    fos:hledger: || 0.25
    fos:hledger:config file || 2.25
    per:fin: || 0.50

    $ hledger bal -DN --pivot=t

    || 2024-06-18
    ===++============
    c || 0.50
    e || 2.25
    l || 0.50
    s || 0.25

    etc

    5/

    #hledger #plaintextaccounting #timetrackingsoftware

  15. Sample reports:

    $ hledger bal -DN --pivot=acct:p

    || 2024-06-18
    =========================++============
    biz:res: || 0.50
    fos:hledger: || 0.25
    fos:hledger:config file || 2.25
    per:fin: || 0.50

    $ hledger bal -DN --pivot=t

    || 2024-06-18
    ===++============
    c || 0.50
    e || 2.25
    l || 0.50
    s || 0.25

    etc

    5/

  16. Sample reports:

    $ hledger bal -DN --pivot=acct:p

    || 2024-06-18
    =========================++============
    biz:res: || 0.50
    fos:hledger: || 0.25
    fos:hledger:config file || 2.25
    per:fin: || 0.50

    $ hledger bal -DN --pivot=t

    || 2024-06-18
    ===++============
    c || 0.50
    e || 2.25
    l || 0.50
    s || 0.25

    etc

    5/

    #hledger #plaintextaccounting #timetrackingsoftware

  17. Sample reports:

    $ hledger bal -DN --pivot=acct:p

    || 2024-06-18
    =========================++============
    biz:res: || 0.50
    fos:hledger: || 0.25
    fos:hledger:config file || 2.25
    per:fin: || 0.50

    $ hledger bal -DN --pivot=t

    || 2024-06-18
    ===++============
    c || 0.50
    e || 2.25
    l || 0.50
    s || 0.25

    etc

    5/

    #hledger #plaintextaccounting #timetrackingsoftware

  18. Sample reports:

    $ hledger bal -DN --pivot=acct:p

    || 2024-06-18
    =========================++============
    biz:res: || 0.50
    fos:hledger: || 0.25
    fos:hledger:config file || 2.25
    per:fin: || 0.50

    $ hledger bal -DN --pivot=t

    || 2024-06-18
    ===++============
    c || 0.50
    e || 2.25
    l || 0.50
    s || 0.25

    etc

    5/

    #hledger #plaintextaccounting #timetrackingsoftware

  19. My t: meanings are (could be anything):

    tag t ; Time-tracking activity type
    ; (c)leaning up debt, fixing issues
    ; (e)nhancing
    ; (l)earning
    ; (s)upporting

    4/

    #hledger #plaintextaccounting #timetrackingsoftware

  20. My t: meanings are (could be anything):

    tag t ; Time-tracking activity type
    ; (c)leaning up debt, fixing issues
    ; (e)nhancing
    ; (l)earning
    ; (s)upporting

    4/

  21. My t: meanings are (could be anything):

    tag t ; Time-tracking activity type
    ; (c)leaning up debt, fixing issues
    ; (e)nhancing
    ; (l)earning
    ; (s)upporting

    4/

    #hledger #plaintextaccounting #timetrackingsoftware

  22. My t: meanings are (could be anything):

    tag t ; Time-tracking activity type
    ; (c)leaning up debt, fixing issues
    ; (e)nhancing
    ; (l)earning
    ; (s)upporting

    4/

    #hledger #plaintextaccounting #timetrackingsoftware

  23. My t: meanings are (could be anything):

    tag t ; Time-tracking activity type
    ; (c)leaning up debt, fixing issues
    ; (e)nhancing
    ; (l)earning
    ; (s)upporting

    4/

    #hledger #plaintextaccounting #timetrackingsoftware

  24. Eg, from my timedot log:

    ** 2024-06-18 Tue
    biz.res ll
    fos.hledger eeee eeee e ; p:config file
    fos.hledger s
    per.fin cc

    which is read as (using --alias ‘/\./=:’):

    2024-06-18 * Tue
    (biz:res) 0.50 ; t:l
    (fos:hledger) 2.25 ; p:config file, t:e
    (fos:hledger) 0.25 ; t:s
    (per:fin) 0.50 ; t:c

    3/

    #hledger #plaintextaccounting #timetrackingsoftware

  25. Eg, from my timedot log:

    ** 2024-06-18 Tue
    biz.res ll
    fos.hledger eeee eeee e ; p:config file
    fos.hledger s
    per.fin cc

    which is read as (using --alias ‘/\./=:’):

    2024-06-18 * Tue
    (biz:res) 0.50 ; t:l
    (fos:hledger) 2.25 ; p:config file, t:e
    (fos:hledger) 0.25 ; t:s
    (per:fin) 0.50 ; t:c

    3/

  26. Eg, from my timedot log:

    ** 2024-06-18 Tue
    biz.res ll
    fos.hledger eeee eeee e ; p:config file
    fos.hledger s
    per.fin cc

    which is read as (using --alias ‘/\./=:’):

    2024-06-18 * Tue
    (biz:res) 0.50 ; t:l
    (fos:hledger) 2.25 ; p:config file, t:e
    (fos:hledger) 0.25 ; t:s
    (per:fin) 0.50 ; t:c

    3/

    #hledger #plaintextaccounting #timetrackingsoftware

  27. Eg, from my timedot log:

    ** 2024-06-18 Tue
    biz.res ll
    fos.hledger eeee eeee e ; p:config file
    fos.hledger s
    per.fin cc

    which is read as (using --alias ‘/\./=:’):

    2024-06-18 * Tue
    (biz:res) 0.50 ; t:l
    (fos:hledger) 2.25 ; p:config file, t:e
    (fos:hledger) 0.25 ; t:s
    (per:fin) 0.50 ; t:c

    3/

    #hledger #plaintextaccounting #timetrackingsoftware

  28. Eg, from my timedot log:

    ** 2024-06-18 Tue
    biz.res ll
    fos.hledger eeee eeee e ; p:config file
    fos.hledger s
    per.fin cc

    which is read as (using --alias ‘/\./=:’):

    2024-06-18 * Tue
    (biz:res) 0.50 ; t:l
    (fos:hledger) 2.25 ; p:config file, t:e
    (fos:hledger) 0.25 ; t:s
    (per:fin) 0.50 ; t:c

    3/

    #hledger #plaintextaccounting #timetrackingsoftware

  29. Still, it's nifty; I'm now using three dimensions of categorisation:

    1. account name ("time category", must be declared)
    2. t: "activity type" tag (implied by the letter used for logging)
    3. p: "project description" explicit tag (like a subaccount but more ad hoc and exempt from account checking)

    and I can show any of them with hledger -f $TIMELOG bal, bal --pivot p, --pivot:acct:p, --pivot:acct:p:t, etc.

    2/

    #hledger #plaintextaccounting #timetrackingsoftware

  30. Still, it's nifty; I'm now using three dimensions of categorisation:

    1. account name ("time category", must be declared)
    2. t: "activity type" tag (implied by the letter used for logging)
    3. p: "project description" explicit tag (like a subaccount but more ad hoc and exempt from account checking)

    and I can show any of them with hledger -f $TIMELOG bal, bal --pivot p, --pivot:acct:p, --pivot:acct:p:t, etc.

    2/

  31. Still, it's nifty; I'm now using three dimensions of categorisation:

    1. account name ("time category", must be declared)
    2. t: "activity type" tag (implied by the letter used for logging)
    3. p: "project description" explicit tag (like a subaccount but more ad hoc and exempt from account checking)

    and I can show any of them with hledger -f $TIMELOG bal, bal --pivot p, --pivot:acct:p, --pivot:acct:p:t, etc.

    2/

    #hledger #plaintextaccounting #timetrackingsoftware

  32. Still, it's nifty; I'm now using three dimensions of categorisation:

    1. account name ("time category", must be declared)
    2. t: "activity type" tag (implied by the letter used for logging)
    3. p: "project description" explicit tag (like a subaccount but more ad hoc and exempt from account checking)

    and I can show any of them with hledger -f $TIMELOG bal, bal --pivot p, --pivot:acct:p, --pivot:acct:p:t, etc.

    2/

    #hledger #plaintextaccounting #timetrackingsoftware

  33. Still, it's nifty; I'm now using three dimensions of categorisation:

    1. account name ("time category", must be declared)
    2. t: "activity type" tag (implied by the letter used for logging)
    3. p: "project description" explicit tag (like a subaccount but more ad hoc and exempt from account checking)

    and I can show any of them with hledger -f $TIMELOG bal, bal --pivot p, --pivot:acct:p, --pivot:acct:p:t, etc.

    2/

    #hledger #plaintextaccounting #timetrackingsoftware

  34. I've started using tags for added categorisation in my timedot file, to reduce the busywork of declaring subaccounts (declarations are required since I check account names for typos with hledger -f $TIMELOG check -s).

    But if there was a way to relax account checking below a certain depth, I'd have probably kept using subaccounts, for simplicity.

    1/

    #hledger #plaintextaccounting #timetrackingsoftware

  35. I've started using tags for added categorisation in my timedot file, to reduce the busywork of declaring subaccounts (declarations are required since I check account names for typos with hledger -f $TIMELOG check -s).

    But if there was a way to relax account checking below a certain depth, I'd have probably kept using subaccounts, for simplicity.

    1/

  36. I've started using tags for added categorisation in my timedot file, to reduce the busywork of declaring subaccounts (declarations are required since I check account names for typos with hledger -f $TIMELOG check -s).

    But if there was a way to relax account checking below a certain depth, I'd have probably kept using subaccounts, for simplicity.

    1/

    #hledger #plaintextaccounting #timetrackingsoftware

  37. I've started using tags for added categorisation in my timedot file, to reduce the busywork of declaring subaccounts (declarations are required since I check account names for typos with hledger -f $TIMELOG check -s).

    But if there was a way to relax account checking below a certain depth, I'd have probably kept using subaccounts, for simplicity.

    1/

    #hledger #plaintextaccounting #timetrackingsoftware

  38. I've started using tags for added categorisation in my timedot file, to reduce the busywork of declaring subaccounts (declarations are required since I check account names for typos with hledger -f $TIMELOG check -s).

    But if there was a way to relax account checking below a certain depth, I'd have probably kept using subaccounts, for simplicity.

    1/

    #hledger #plaintextaccounting #timetrackingsoftware

  39. Thank you, TechRepublic, for the advice and instructions on using our Time and Costs module!

    Read the article and learn how to log time on an activity within a project. You will see how much time you spent on different work packages.

    techrepublic.com/article/how-t

    #timetrackingsoftware #openproject #opensourcesoftware #techrepublic

  40. Thank you, TechRepublic, for the advice and instructions on using our Time and Costs module!

    Read the article and learn how to log time on an activity within a project. You will see how much time you spent on different work packages.

    techrepublic.com/article/how-t

  41. Thank you, TechRepublic, for the advice and instructions on using our Time and Costs module!

    Read the article and learn how to log time on an activity within a project. You will see how much time you spent on different work packages.

    techrepublic.com/article/how-t

    #timetrackingsoftware #openproject #opensourcesoftware #techrepublic

  42. Thank you, TechRepublic, for the advice and instructions on using our Time and Costs module!

    Read the article and learn how to log time on an activity within a project. You will see how much time you spent on different work packages.

    techrepublic.com/article/how-t

    #timetrackingsoftware #openproject #opensourcesoftware #techrepublic

  43. Thank you, TechRepublic, for the advice and instructions on using our Time and Costs module!

    Read the article and learn how to log time on an activity within a project. You will see how much time you spent on different work packages.

    techrepublic.com/article/how-t

    #timetrackingsoftware #openproject #opensourcesoftware #techrepublic