[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eYou can create a new issue in the Issue Tracker by sending an email to the designated email alias, \u003ccode\u003ebuganizer-system+componentID@google.com\u003c/code\u003e, replacing \u003ccode\u003ecomponentID\u003c/code\u003e with the relevant component's ID.\u003c/p\u003e\n"],["\u003cp\u003eThe email must be sent from an account with Issue Tracker access, and the subject line becomes the issue title, while the email body serves as the initial comment describing the issue.\u003c/p\u003e\n"],["\u003cp\u003eOptionally, you can attach files like screenshots to provide additional context for the reported issue.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your domain supports SPF and DKIM for this functionality; otherwise, use the Issue Tracker UI to create issues.\u003c/p\u003e\n"]]],[],null,["# Create a New Issue by Email\n\nThis page describes how to create a new issue by sending an email to the Issue\nTracker email alias.\n\nBefore you begin:\n-----------------\n\n- Make sure your domain supports [SPF](https://support.google.com/a/answer/178723) and [DKIM](https://support.google.com/a/answer/174124). If your domain does not support them, [create the issue with the Issue Tracker UI](/issue-tracker/guides/create-issue-ui).\n\nCreate the issue:\n-----------------\n\nTo create a new issue by email:\n\n1. From account.\n\n To create an issue by email, the message must be sent from an account that\n has Issue Tracker access. If your account does not have access, you cannot\n bypass this restriction by forwarding the message to an account with access.\n2. Address the email.\n\n Use the following format for the email address:\n\n `buganizer-system+componentID@google.com`\n\n where *`componentID`* is the [ID number of the component](../concepts/components) where you want\n to report the issue.\n3. (Optional) Add a subject line to the email.\n\n Make the subject line a succinct description of the issue you are reporting.\n The subject becomes the title of the issue and is the first thing visible\n both in Issue Tracker searches and on the page dedicated to the issue.\n | If you don't add a subject line, Issue Tracker uses the first 30 characters of the email body as the issue title.\n4. Add text to the body of the email.\n\n Provide a full description of the issue you are reporting, including details\n such as why it is an issue, the specific circumstances in which you\n encountered the issue, and how the issue can be reproduced by someone else.\n This information appears as the first comment on the dedicated issue page.\n5. (Optional) Add attachments to the email.\n\n Include any attachments, such as screenshots, that help others understand\n and evaluate the issue. Attachments appear in the first comment on the\n dedicated issue page.\n\nWhat's next\n-----------\n\n- [Concept: Components](../concepts/components)\n- [Concept: Issues](../concepts/issues)\n- [Viewing/editing an issue with the Issue Tracker UI](/issue-tracker/guides/edit-issue-ui)\n- [Editing an issue by email](/issue-tracker/guides/edit-issue-email)"]]