JIRA-ISSUE-WORKLOG-ADD(7)

πŸ“¦ version 1.7.0, in nixos 26.05, nixpkgs unstable

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 with JIRA_CONFIG_FILE env 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