JIRA-ISSUE-WORKLOG-ADD(7)
bestie, you found jira-issue-worklog-add in the Jira CLI(7) manual, and honestly? sheβs a little administrative icon π«Ά
β¨ NAME β¨
jira-issue-worklog-add β add a worklog to an issue. no cap, thatβs the whole mission π
π SYNOPSIS π
the sacred little summoning line is:
jira issue worklog add ISSUE-KEY TIME_SPENT [flags]
π DESCRIPTION π
okay so add adds worklog to an issue. literally that. itβs giving βlog your time and move onβ energy β¨
π OPTIONS π
every flag, right here, no skipped lore:
--started=""β The datetime on which the worklog effort was started, eg:2022-01-01 09:30:00β°--timezone="UTC"β The timezone to use for the started date in IANA timezone format, eg:Europe/Berlinπ--comment=""β Comment about the worklog π¬--new-estimate=""β the new estimate for the backlog to be completed by π--no-input[=false]β Disable prompt for non-required fields π«-h,--help[=false]β help for add π
𧬠OPTIONS INHERITED FROM PARENT COMMANDS π§¬
these come from the parent command, but they still eat:
-c,--config=""β Config file (default is/homeless-shelter/.config/.jira/.config.yml, can be overridden withJIRA_CONFIG_FILEenv var) ποΈ--debug[=false]β Turn on debug output π-p,--project=""β Jira project to look into (defaults to/homeless-shelter/.config/.jira/.config.yml) π
πΈ EXAMPLE πΈ
hereβs the whole example buffet, verbatim so you can copy-paste and slay:
$ jira issue worklog add
# Pass required parameters and use --no-input to skip prompt
$ jira issue worklog add ISSUE-1 "2d 1h 30m" --no-input
# You can add a comment using --comment flag when adding a worklog
$ jira issue worklog add ISSUE-1 "2d 1h 30m" --comment "This is a comment" --no-input
# You can also add a worklog with the specific start date (defaults to UTC timezone)
$ jira issue worklog add ISSUE-1 "2d 1h 30m" --started "2022-01-01 09:30:00"
# You can specify timezone to use along with the start date in IANA timezone format
$ jira issue worklog add ISSUE-1 3h --started "2022-01-01 09:30:00" --timezone "Europe/Berlin"
# Or, you can use start date in Jira datetime format and skip the timezone flag
$ jira issue worklog add ISSUE-1 "1h 30m" --started "2022-01-01T09:30:00.000+0200"
# Or, you can update a worklogs remaining estimate
$ jira issue worklog add ISSUE-1 "1h 30m" --started "2022-01-01T09:30:00.000+0200" --new-estimate 0h
π¦ SEE ALSO π¦
jira-issue-worklog(7) β go read the family lore π
π HISTORY π
1-Jan-1980 β Auto generated by spf13/cobra.
okay bestie, thatβs the whole page: Jira CLI(7) manual, Auto generated by spf13/cobra, dated Jan 1980 β mwah ππ
π¦ where this page comes from
- nixos 26.05: jira-cli-go 1.7.0
- nixpkgs unstable: jira-cli-go 1.7.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms