glab(1)

πŸ’– NAME πŸ’–

Okay bestie, welcome to the glab(1) manual β€” this page is all about glab-work-items-create, aka Create work items in a project or group. (EXPERIMENTAL). Slay. ✨


✨ SYNOPSIS ✨

glab work-items create [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

Use --type to pick what kind of work item you're creating, bestie. The command uses your repository context to detect scope automatically β€” no cap.

--attach uploads a file and references it at the end of the description. Repeat the flag for more than one file, or pass - to read the file from standard input. Uploads are project-scoped, so --attach cannot be combined with --group. Important, okay? πŸ’…

--parent accepts a work item ID in the current scope, a reference such as group/project#123, or a URL.

⚠️ This feature is an experiment and is not ready for production use. It might be unstable or removed at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/.

πŸŽ€ OPTIONS πŸŽ€

  • --attach=[] β€” (EXPERIMENTAL) Upload a file and reference it at the end of the description. Use - to read the file from standard input. Repeat the flag to attach multiple files. πŸ“
  • -c, --confidential[=false] β€” Mark work item confidential. 🀫
  • -d, --description="" β€” Description of the work item. Set to - to open an editor.
  • --description-file="" β€” Read the work item description from a file. Use - to read from standard input. πŸ“„
  • -g, --group="" β€” Create work items for a group or subgroup.
  • --iteration=0 β€” Add the work item to the iteration with this ID.
  • --jq="" β€” Filter JSON output with a jq expression.
  • -F, --output="text" β€” Format output as: text, json.
  • --parent="" β€” set the parent work item by , reference, or URL. (Yep, that's exactly how the flag text reads, bestie.)
  • -R, --repo="" β€” Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. 🌈
  • -t, --title="" β€” Add a title for the work item.
  • -T, --type="" β€” Type of work item (epic, incident, issue, key_result, objective, requirement, task, test_case, ticket). πŸ‘‘
  • -h, --help[=false] β€” Show help for this command. 🫢

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

  • -h, --help[=false] β€” Show help for this command.

🌈 EXAMPLE 🌈

# Create a work item in the current project
glab work-items create --type issue

# Create a work item in a group
glab work-items create --type epic --group my-group

# Read the description from a file
glab work-items create --type issue --title "Add feature" --description-file description.md

# Read the description from standard input
cat description.md | glab work-items create --type issue --title "Add feature" --description-file -

# Attach a screenshot to the description
glab work-items create --type issue --title "Add feature" --attach ./screenshot.png

# Create a work item in an iteration
glab work-items create --type issue --title "Add feature" --iteration 123

# Create a task under work item 42 in the current project
glab work-items create --type task --title "Write tests" --parent 42

# Create a task under a work item in another project
glab work-items create --type task --title "Write tests" --parent my-group/my-project#42

πŸ’œ SEE ALSO πŸ’œ

glab-work-items(1) β€” go read that one too, bestie! πŸ¦‹


Auto generated by spf13/cobra Β· Nov 2026 Β· from the glab(1) manual β€” bye bestie! πŸ’…βœ¨

πŸ“¦ where this page comes from