Creating an issue

Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.

People with read permissions can create an issue in a repository where issues are enabled.

Issues can be used to keep track of bugs, enhancements, or other requests. For more information, see "About issues."

Repository administrators can disable issues for a repository. For more information, see "Disabling issues."

Creating an issue from a repository

  1. En GitHub Enterprise, visita la página principal del repositorio.
  2. Debajo del nombre de tu repositorio, da clic en Informe de problemas. Pestaña de informe de problemas
  3. Click New issue. New Issues button
  4. If your repository uses issue templates, click Get started next to the type of issue you'd like to open. Select the type of issue you want to create Or, click Open a blank issue if the type of issue you'd like to open isn't included in the available options. Link to open a blank issue
  5. Teclea un título y descripción para tu informe de problemas. Un ejemplo de informe de problemas
  6. Si eres un mantenedor de proyecto, puedes asignar el informe de problemas a alguien, agregarlo a un tablero de proyecto, asociarlo con un hito, o aplicar una etiqueta.
  7. Cuando termines, da clic en Emitir nuevo informe de problemas.

Creating an issue with CLI de GitHub

CLI de GitHub is an open source tool for using GitHub Enterprise from your computer's command line. When you're working from the command line, you can use the CLI de GitHub to save time and avoid switching context. To learn more about CLI de GitHub, see "About CLI de GitHub."

To create an issue, use the gh issue create subcommand. To skip the interactive prompts, include the --body and the --title flags.

gh issue create --title "My new issue" --body "Here are more details."

You can also specify assignees, labels, milestones, and projects.

gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase"

Creating an issue from a comment

You can open a new issue from a comment in an issue or pull request. When you open an issue from a comment, the issue contains a snippet showing where the comment was originally posted.

  1. Navigate to the comment that you would like to open an issue from.
  2. In that comment, click . Kebab button in pull request review comment
  3. Click Reference in new issue. Reference in new issue menu item
  4. Use the "Repository" drop-down menu, and select the repository you want to open the issue in. Repository dropdown for new issue
  5. Type a descriptive title and body for the issue. Title and body for new issue
  6. Click Create issue. Button to create new issue
  7. Si eres un mantenedor de proyecto, puedes asignar el informe de problemas a alguien, agregarlo a un tablero de proyecto, asociarlo con un hito, o aplicar una etiqueta.
  8. Cuando termines, da clic en Emitir nuevo informe de problemas.

Creating an issue from code

You can open a new issue from a specific line or lines of code in a file or pull request. When you open an issue from code, the issue contains a snippet showing the line or range of code you chose. You can only open an issue in the same repository where the code is stored.

Code snippet rendered in an issue opened from code

  1. En GitHub Enterprise, visita la página principal del repositorio.
  2. Locate the code you want to reference in an issue:
    • To open an issue about code in a file, navigate to the file.
    • To open an issue about code in a pull request, navigate to the pull request and click Files changed. Then, browse to the file that contains the code you want include in your comment, and click View.
  3. Decide si seleccionar una única línea o un rango:
    • Para seleccionar una única línea del código, haz clic en el número de línea para resaltarla. Archivo con una única línea del código seleccionada
      • Para seleccionar un rango de código, haz clic en el número de la primera línea del rango para resaltar la línea del código. Luego lleva el puntero hasta la última línea del rango del código, presiona Shift y haz clic en el número de línea para resaltar el rango. Archivo con un rango del código seleccionado
  4. To the left of the code range, click . In the drop-down menu, click Reference in new issue. Kebab menu with option to open a new issue from a selected line
  5. Teclea un título y descripción para tu informe de problemas. Un ejemplo de informe de problemas
  6. Si eres un mantenedor de proyecto, puedes asignar el informe de problemas a alguien, agregarlo a un tablero de proyecto, asociarlo con un hito, o aplicar una etiqueta.
  7. Cuando termines, da clic en Emitir nuevo informe de problemas.

Creating an issue from a project board note

If you're using a project board to track and prioritize your work, you can convert project board notes to issues. For more information, see "About project boards" and "Adding notes to a project board."

Creating an issue from a URL query

You can use query parameters to open issues. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or an issue template on GitHub. To create your own query parameters, you must match the key and value pair.

Tip: You can also create issue templates that open with default labels, assignees, and an issue title. For more information, see "Using templates to encourage useful issues and pull requests."

You must have the proper permissions for any action to use the equivalent query parameter. For example, you must have permission to add a label to an issue to use the labels query parameter. For more information, see "Repository permission levels for an organization."

If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a 404 Not Found error page. If you create a URL that exceeds the server limit, the URL will return a 414 URI Too Long error page.

Query parameterExample
titlehttps://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report creates an issue with the label "bug" and title "New bug report."
bodyhttps://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem. creates an issue with the title "New bug report" and the comment "Describe the problem" in the issue body.
labelshttps://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug creates an issue with the labels "help wanted" and "bug".
milestonehttps://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones creates an issue with the milestone "testing milestones."
assigneeshttps://github.com/octo-org/octo-repo/issues/new?assignees=octocat creates an issue and assigns it to @octocat.
projectshttps://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1 creates an issue with the title "Bug fix" and adds it to the organization's project board 1.
templatehttps://github.com/octo-org/octo-repo/issues/new?template=issue_template.md creates an issue with a template in the issue body. The template query parameter works with templates stored in an ISSUE_TEMPLATE subdirectory within the root, docs/ or .github/ directory in a repository. For more information, see "Using templates to encourage useful issues and pull requests."

Further reading

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.