JIRA-ISSUE-CLONE(7)

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

πŸ’… jira-issue-clone(7) β€” the Jira CLI glow-up manual

okay so bestie, welcome to the jira-issue-clone page of the Jira CLI manual (that's section 7, iykyk). Sit down, grab a strawberry drink πŸ“, and let's get into it.


✨ NAME ✨

jira-issue-clone β€” clone duplicates an issue 🫢

Like, it makes a copy. A twin. A duplicate. Slay.


🌸 SYNOPSIS 🌸

jira issue clone ISSUE-KEY [flags]

That's the whole shape of it β€” you hand it an ISSUE-KEY, you optionally hand it some [flags], and it does its thing. Iconic behaviour, honestly.


πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here's the vibe: this command duplicates an issue πŸ’– and it also lets you override some of the metadata while it's doing that. So you're not just copy-pasting the whole thing unchanged β€” you get to tweak the details as it clones. The way that works is genuinely so useful, no cap.


πŸŽ€ OPTIONS πŸŽ€

  • -P, --parent="" β€” the parent issue key πŸ‘‘ (defaults to empty, "")
  • -s, --summary="" β€” the issue summary, aka the title 🏷️ (default "")
  • -y, --priority="" β€” the issue priority ⚑ (default "")
  • -a, --assignee="" β€” who gets assigned, as an email or a display name πŸ™‹β€β™€οΈ (default "")
  • -l, --label=[] β€” the issue labels 🏷️🏷️ (list, defaults to empty [])
  • -C, --component=[] β€” the issue components 🧩 (list, defaults to empty [])
  • -H, --replace=[] β€” replace strings in the summary and body. The format is :, like "find me:replace with me" πŸ” β€” literally find, colon, replace, that's it. (list, defaults to empty [])
  • --web[=false] β€” open it in the web browser after a successful clone 🌐 (defaults to false)
  • -h, --help[=false] β€” help for clone 😭 the classic (defaults to false)

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

These ones aren't from clone itself, they come down from the parent commands β€” still yours to use tho πŸ’œ

  • -c, --config="" β€” config file. Default is /homeless-shelter/.config/.jira/.config.yml, and it can be overridden with the JIRA_CONFIG_FILE env var ⭐
  • --debug[=false] β€” turn on debug output πŸ› (defaults to false)
  • -p, --project="" β€” which Jira project to look into. It defaults to /homeless-shelter/.config/.jira/.config.yml πŸ“

🌈 EXAMPLE 🌈

Bestie, examples are the moment. Here we go:

$ jira issue clone ISSUE-1

Just a plain clone. Simple. Beautiful. Ate. πŸ’…

# Clone issue and modify the summary, priority and assignee
$ jira issue clone ISSUE-1 -s"Modified summary" -yHigh -a$(jira me)

Look at that β€” new summary, priority bumped to High, and assignee set to whatever jira me gives you. Main character energy πŸ”₯

# Clone issue and replace text from summary and description
$ jira issue clone ISSUE-1 -H"find me:replace with me"

The -H flag doing its find-and-replace thing across the summary and description. Obsessed. πŸ¦‹


πŸ”₯ SEE ALSO πŸ”₯


πŸ’€ HISTORY πŸ’€

1-Jan-1980 β€” Auto generated by spf13/cobra. Not me being older than everyone here πŸ˜­πŸ™ˆ


ngl bestie, this whole page is Auto generated by spf13/cobra, dated Jan 1980, from the Jira CLI(7) manual. So if something looks weird, blame the generator, not me πŸ’– πŸŽ€ ✨
πŸ“¦ where this page comes from