--- title: '`glab issue create`' stage: AI Clients group: Developer Clients info: To determine the technical writer assigned to the Stage/Group associated with this page, see --- Create an issue. ## Synopsis Opens an editor to draft the issue unless you pass a title and description. Use `--web` to create the issue in your browser, or `--template` to start from an issue template. `--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. An attachment satisfies the description requirement, so `--title` with `--attach` completes without prompting. The `--attach` flag is an experiment. It might be unstable or removed at any time, and is not ready for production use. For more information, see . The `--recover` flag is an experiment: it might be unstable or removed at any time, and is not ready for production use. For more information, see . ```plaintext glab issue create [flags] ``` ## Aliases ```plaintext new ``` ## Examples ```console glab issue create glab issue new glab issue create -m release-2.0.0 -t "we need this feature" --label important glab issue new -t "Fix CVE-YYYY-XXXX" -l security --linked-mr 123 glab issue create -m release-1.0.1 -t "security fix" --label security --web --recover glab issue create -t "Bug Report" --template bug glab issue create -t "Feature Request" --template feature_proposal.md --yes # Use a template file from outside the repository glab issue create -t "Bug Report" --template ~/team-templates/bug.md # Read the description from a file glab issue create -t "we need this feature" --description-file description.md # Read the description from standard input cat description.md | glab issue create -t "we need this feature" --description-file - # Attach a screenshot to the description glab issue create -t "Login button misaligned" -d "See below." --attach ./screenshot.png ``` ## Options ```plaintext -a, --assignee usernames Assign issue to people by their usernames. Multiple usernames can be comma-separated or specified by repeating the flag. --attach stringArray (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 Set an issue to be confidential. -d, --description string Issue description. Set to "-" to open an editor. --description-file string Read the issue description from a file. Use "-" to read from standard input. --due-date string A date in 'YYYY-MM-DD' format. --epic int ID of the epic to add the issue to. -l, --label strings Add label by name. Multiple labels can be comma-separated or specified by repeating the flag. --link-type string Type for the issue link. (default "relates_to") --linked-issues ints The IIDs of issues that this issue links to. Multiple IIDs can be comma-separated or specified by repeating the flag. --linked-mr int The IID of a merge request in which to resolve all issues. -m, --milestone string The global ID or title of a milestone to assign. --no-editor Don't open editor to enter a description. If set to true, uses prompt. --recover Save the options to a file if the issue fails to be created. If the file exists, the options will be loaded from the recovery file. (EXPERIMENTAL) --template string Template to pre-populate the description. A name is looked up in '.gitlab/issue_templates/' of the local repository, and the '.md' extension is optional. A value that is absolute or contains a path separator is read as a file path, for example '~/templates/bug.md'. -e, --time-estimate string Set time estimate for the issue. -s, --time-spent string Set time spent for the issue. -t, --title string Issue title. --web Continue issue creation with web interface. -w, --weight int Issue weight. Valid values are greater than or equal to 0. -y, --yes Don't prompt for confirmation to submit the issue. ``` ## Options inherited from parent commands ```plaintext -h, --help Show help for this command. -R, --repo string Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. ```