CINXE.COM

<!doctype html><html lang="en-US" prefix="og: https://ogp.me/ns#"><head><meta charSet="utf-8"/><meta name="viewport" content="width=device-width,initial-scale=1"/><link rel="icon" href="https://developer.mozilla.org/favicon-48x48.bc390275e955dacb2e65.png"/><link rel="apple-touch-icon" href="https://developer.mozilla.org/apple-touch-icon.528534bba673c38049c2.png"/><meta name="theme-color" content="#ffffff"/><link rel="manifest" href="https://developer.mozilla.org/manifest.f42880861b394dd4dc9b.json"/><link rel="search" type="application/opensearchdescription+xml" href="/opensearch.xml" title="MDN Web Docs"/><title>Creating and working on issues - MDN Web Docs | MDN</title><link rel="alternate" title="Erstellen und Bearbeiten von Issues" href="https://developer.mozilla.org/de/docs/MDN/Community/Issues" hrefLang="de"/><link rel="alternate" title="Bonnes pratiques GitHub pour MDN" href="https://developer.mozilla.org/fr/docs/MDN/Community/Issues" hrefLang="fr"/><link rel="alternate" title="課題の作成と作業のガイドライン" href="https://developer.mozilla.org/ja/docs/MDN/Community/Issues" hrefLang="ja"/><link rel="alternate" title="Как сообщить о проблеме в MDN" href="https://developer.mozilla.org/ru/docs/MDN/Community/Issues" hrefLang="ru"/><link rel="alternate" title="创建和解决议题指南" href="https://developer.mozilla.org/zh-CN/docs/MDN/Community/Issues" hrefLang="zh"/><link rel="alternate" title="Creating and working on issues" href="https://developer.mozilla.org/en-US/docs/MDN/Community/Issues" hrefLang="en"/><link rel="preload" as="font" type="font/woff2" href="/static/media/Inter.var.c2fe3cb2b7c746f7966a.woff2" crossorigin=""/><link rel="alternate" type="application/rss+xml" title="MDN Blog RSS Feed" href="https://developer.mozilla.org/en-US/blog/rss.xml" hrefLang="en"/><meta name="description" content="As a contributor, you can report and work on issues. After you report an issue, the issue gets triaged. Issue triaging is typically done by people assigned the role of a maintainer or an owner."/><meta property="og:url" content="https://developer.mozilla.org/en-US/docs/MDN/Community/Issues"/><meta property="og:title" content="Creating and working on issues - MDN Web Docs | MDN"/><meta property="og:type" content="website"/><meta property="og:locale" content="en_US"/><meta property="og:description" content="As a contributor, you can report and work on issues. After you report an issue, the issue gets triaged. Issue triaging is typically done by people assigned the role of a maintainer or an owner."/><meta property="og:image" content="https://developer.mozilla.org/mdn-social-share.d893525a4fb5fb1f67a2.png"/><meta property="og:image:type" content="image/png"/><meta property="og:image:height" content="1080"/><meta property="og:image:width" content="1920"/><meta property="og:image:alt" content="The MDN Web Docs logo, featuring a blue accent color, displayed on a solid black background."/><meta property="og:site_name" content="MDN Web Docs"/><meta name="twitter:card" content="summary_large_image"/><meta name="twitter:creator" content="MozDevNet"/><link rel="canonical" href="https://developer.mozilla.org/en-US/docs/MDN/Community/Issues"/><style media="print">.article-actions-container,.document-toc-container,.language-menu,.main-menu-toggle,.on-github,.page-footer,.place,.sidebar,.top-banner,.top-navigation-main,ul.prev-next{display:none!important}.main-page-content,.main-page-content pre{padding:2px}.main-page-content pre{border-left-width:2px}</style><script src="/static/js/gtag.js" defer=""></script><script defer="" src="/static/js/main.a44547d8.js"></script><link href="/static/css/main.6ca4d473.css" rel="stylesheet"/></head><body><script>if(document.body.addEventListener("load",(t=>{t.target.classList.contains("interactive")&&t.target.setAttribute("data-readystate","complete")}),{capture:!0}),window&&document.documentElement){const t={light:"#ffffff",dark:"#1b1b1b"};try{const e=window.localStorage.getItem("theme");e&&(document.documentElement.className=e,document.documentElement.style.backgroundColor=t[e]);const o=window.localStorage.getItem("nop");o&&(document.documentElement.dataset.nop=o)}catch(t){console.warn("Unable to read theme from localStorage",t)}}</script><div id="root"><ul id="nav-access" class="a11y-nav"><li><a id="skip-main" href="#content">Skip to main content</a></li><li><a id="skip-search" href="#top-nav-search-input">Skip to search</a></li><li><a id="skip-select-language" href="#languages-switcher-button">Skip to select language</a></li></ul><div class="page-wrapper document-page"><div class="top-banner loading"><section class="place top container"></section></div><div class="sticky-header-container"><header class="top-navigation "><div class="container "><div class="top-navigation-wrap"><a href="/en-US/" class="logo" aria-label="MDN homepage"><svg id="mdn-docs-logo" xmlns="http://www.w3.org/2000/svg" x="0" y="0" viewBox="0 0 694.9 104.4" style="enable-background:new 0 0 694.9 104.4" xml:space="preserve" role="img"><title>MDN Web Docs</title><path d="M40.3 0 11.7 92.1H0L28.5 0h11.8zm10.4 0v92.1H40.3V0h10.4zM91 0 62.5 92.1H50.8L79.3 0H91zm10.4 0v92.1H91V0h10.4z" class="logo-m"></path><path d="M627.9 95.6h67v8.8h-67v-8.8z" class="logo-_"></path><path d="M367 42h-4l-10.7 30.8h-5.5l-10.8-26h-.4l-10.5 26h-5.2L308.7 42h-3.8v-5.6H323V42h-6.5l6.8 20.4h.4l10.3-26h4.7l11.2 26h.5l5.7-20.3h-6.2v-5.6H367V42zm34.9 20c-.4 3.2-2 5.9-4.7 8.2-2.8 2.3-6.5 3.4-11.3 3.4-5.4 0-9.7-1.6-13.1-4.7-3.3-3.2-5-7.7-5-13.7 0-5.7 1.6-10.3 4.7-14s7.4-5.5 12.9-5.5c5.1 0 9.1 1.6 11.9 4.7s4.3 6.9 4.3 11.3c0 1.5-.2 3-.5 4.7h-25.6c.3 7.7 4 11.6 10.9 11.6 2.9 0 5.1-.7 6.5-2 1.5-1.4 2.5-3 3-4.9l6 .9zM394 51.3c.2-2.4-.4-4.7-1.8-6.9s-3.8-3.3-7-3.3c-3.1 0-5.3 1-6.9 3-1.5 2-2.5 4.4-2.8 7.2H394zm51 2.4c0 5-1.3 9.5-4 13.7s-6.9 6.2-12.7 6.2c-6 0-10.3-2.2-12.7-6.7-.1.4-.2 1.4-.4 2.9s-.3 2.5-.4 2.9h-7.3c.3-1.7.6-3.5.8-5.3.3-1.8.4-3.7.4-5.5V22.3h-6v-5.6H416v27c1.1-2.2 2.7-4.1 4.7-5.7 2-1.6 4.8-2.4 8.4-2.4 4.6 0 8.4 1.6 11.4 4.7 3 3.2 4.5 7.6 4.5 13.4zm-7.7.6c0-4.2-1-7.4-3-9.5-2-2.2-4.4-3.3-7.4-3.3-3.4 0-6 1.2-8 3.7-1.9 2.4-2.9 5-3 7.7V57c0 3 1 5.6 3 7.7s4.5 3.1 7.6 3.1c3.6 0 6.3-1.3 8.1-3.9 1.8-2.7 2.7-5.9 2.7-9.6zm69.2 18.5h-13.2v-7.2c-1.2 2.2-2.8 4.1-4.9 5.6-2.1 1.6-4.8 2.4-8.3 2.4-4.8 0-8.7-1.6-11.6-4.9-2.9-3.2-4.3-7.7-4.3-13.3 0-5 1.3-9.6 4-13.7 2.6-4.1 6.9-6.2 12.8-6.2 5.7 0 9.8 2.2 12.3 6.5V22.3h-8.6v-5.6h15.8v50.6h6v5.5zM493.2 56v-4.4c-.1-3-1.2-5.5-3.2-7.3s-4.4-2.8-7.2-2.8c-3.6 0-6.3 1.3-8.2 3.9-1.9 2.6-2.8 5.8-2.8 9.6 0 4.1 1 7.3 3 9.5s4.5 3.3 7.4 3.3c3.2 0 5.8-1.3 7.8-3.8 2.1-2.6 3.1-5.3 3.2-8zm53.1-1.4c0 5.6-1.8 10.2-5.3 13.7s-8.2 5.3-13.9 5.3-10.1-1.7-13.4-5.1c-3.3-3.4-5-7.9-5-13.5 0-5.3 1.6-9.9 4.7-13.7 3.2-3.8 7.9-5.7 14.2-5.7s11 1.9 14.1 5.7c3 3.7 4.6 8.1 4.6 13.3zm-7.7-.2c0-4-1-7.2-3-9.5s-4.8-3.5-8.2-3.5c-3.6 0-6.4 1.2-8.3 3.7s-2.9 5.6-2.9 9.5c0 3.7.9 6.8 2.8 9.4 1.9 2.6 4.6 3.9 8.3 3.9 3.6 0 6.4-1.3 8.4-3.8 1.9-2.6 2.9-5.8 2.9-9.7zm45 5.8c-.4 3.2-1.9 6.3-4.4 9.1-2.5 2.9-6.4 4.3-11.8 4.3-5.2 0-9.4-1.6-12.6-4.8-3.2-3.2-4.8-7.7-4.8-13.7 0-5.5 1.6-10.1 4.7-13.9 3.2-3.8 7.6-5.7 13.2-5.7 2.3 0 4.6.3 6.7.8 2.2.5 4.2 1.5 6.2 2.9l1.5 9.5-5.9.7-1.3-6.1c-2.1-1.2-4.5-1.8-7.2-1.8-3.5 0-6.1 1.2-7.7 3.7-1.7 2.5-2.5 5.7-2.5 9.6 0 4.1.9 7.3 2.7 9.5 1.8 2.3 4.4 3.4 7.8 3.4 5.2 0 8.2-2.9 9.2-8.8l6.2 1.3zm34.7 1.9c0 3.6-1.5 6.5-4.6 8.5s-7 3-11.7 3c-5.7 0-10.6-1.2-14.6-3.6l1.2-8.8 5.7.6-.2 4.7c1.1.5 2.3.9 3.6 1.1s2.6.3 3.9.3c2.4 0 4.5-.4 6.5-1.3 1.9-.9 2.9-2.2 2.9-4.1 0-1.8-.8-3.1-2.3-3.8s-3.5-1.3-5.8-1.7-4.6-.9-6.9-1.4c-2.3-.6-4.2-1.6-5.7-2.9-1.6-1.4-2.3-3.5-2.3-6.3 0-4.1 1.5-6.9 4.6-8.5s6.4-2.4 9.9-2.4c2.6 0 5 .3 7.2.9 2.2.6 4.3 1.4 6.1 2.4l.8 8.8-5.8.7-.8-5.7c-2.3-1-4.7-1.6-7.2-1.6-2.1 0-3.7.4-5.1 1.1-1.3.8-2 2-2 3.8 0 1.7.8 2.9 2.3 3.6 1.5.7 3.4 1.2 5.7 1.6 2.2.4 4.5.8 6.7 1.4 2.2.6 4.1 1.6 5.7 3 1.4 1.6 2.2 3.7 2.2 6.6zM197.6 73.2h-17.1v-5.5h3.8V51.9c0-3.7-.7-6.3-2.1-7.9-1.4-1.6-3.3-2.3-5.7-2.3-3.2 0-5.6 1.1-7.2 3.4s-2.4 4.6-2.5 6.9v15.6h6v5.5h-17.1v-5.5h3.8V51.9c0-3.8-.7-6.4-2.1-7.9-1.4-1.5-3.3-2.3-5.6-2.3-3.2 0-5.5 1.1-7.2 3.3-1.6 2.2-2.4 4.5-2.5 6.9v15.8h6.9v5.5h-20.2v-5.5h6V42.4h-6.1v-5.6h13.4v6.4c1.2-2.1 2.7-3.8 4.7-5.2 2-1.3 4.4-2 7.3-2s5.3.7 7.5 2.1c2.2 1.4 3.7 3.5 4.5 6.4 1.1-2.5 2.7-4.5 4.9-6.1s4.8-2.4 7.9-2.4c3.5 0 6.5 1.1 8.9 3.3s3.7 5.6 3.7 10.2v18.2h6.1v5.5zm42.5 0h-13.2V66c-1.2 2.2-2.8 4.1-4.9 5.6-2.1 1.6-4.8 2.4-8.3 2.4-4.8 0-8.7-1.6-11.6-4.9-2.9-3.2-4.3-7.7-4.3-13.3 0-5 1.3-9.6 4-13.7 2.6-4.1 6.9-6.2 12.8-6.2s9.8 2.2 12.3 6.5V22.7h-8.6v-5.6h15.8v50.6h6v5.5zm-13.3-16.8V52c-.1-3-1.2-5.5-3.2-7.3s-4.4-2.8-7.2-2.8c-3.6 0-6.3 1.3-8.2 3.9-1.9 2.6-2.8 5.8-2.8 9.6 0 4.1 1 7.3 3 9.5s4.5 3.3 7.4 3.3c3.2 0 5.8-1.3 7.8-3.8 2.1-2.6 3.1-5.3 3.2-8zm61.5 16.8H269v-5.5h6V51.9c0-3.7-.7-6.3-2.2-7.9-1.4-1.6-3.4-2.3-5.7-2.3-3.1 0-5.6 1-7.4 3s-2.8 4.4-2.9 7v15.9h6v5.5h-19.3v-5.5h6V42.4h-6.2v-5.6h13.6V43c2.6-4.6 6.8-6.9 12.7-6.9 3.6 0 6.7 1.1 9.2 3.3s3.7 5.6 3.7 10.2v18.2h6v5.4h-.2z" class="logo-text"></path></svg></a><button title="Open main menu" type="button" class="button action has-icon main-menu-toggle" aria-haspopup="menu" aria-label="Open main menu" aria-expanded="false"><span class="button-wrap"><span class="icon icon-menu "></span><span class="visually-hidden">Open main menu</span></span></button></div><div class="top-navigation-main"><nav class="main-nav" aria-label="Main menu"><ul class="main-menu nojs"><li class="top-level-entry-container "><button type="button" id="references-button" class="top-level-entry menu-toggle" aria-controls="references-menu" aria-expanded="false">References</button><a href="/en-US/docs/Web" class="top-level-entry">References</a><ul id="references-menu" class="submenu references hidden inline-submenu-lg" aria-labelledby="references-button"><li class="apis-link-container mobile-only "><a href="/en-US/docs/Web" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Overview / Web Technology</div><p class="submenu-item-description">Web technology reference for developers</p></div></a></li><li class="html-link-container "><a href="/en-US/docs/Web/HTML" class="submenu-item "><div class="submenu-icon html"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTML</div><p class="submenu-item-description">Structure of content on the web</p></div></a></li><li class="css-link-container "><a href="/en-US/docs/Web/CSS" class="submenu-item "><div class="submenu-icon css"></div><div class="submenu-content-container"><div class="submenu-item-heading">CSS</div><p class="submenu-item-description">Code used to describe document style</p></div></a></li><li class="javascript-link-container "><a href="/en-US/docs/Web/JavaScript" class="submenu-item "><div class="submenu-icon javascript"></div><div class="submenu-content-container"><div class="submenu-item-heading">JavaScript</div><p class="submenu-item-description">General-purpose scripting language</p></div></a></li><li class="http-link-container "><a href="/en-US/docs/Web/HTTP" class="submenu-item "><div class="submenu-icon http"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTTP</div><p class="submenu-item-description">Protocol for transmitting web resources</p></div></a></li><li class="apis-link-container "><a href="/en-US/docs/Web/API" class="submenu-item "><div class="submenu-icon apis"></div><div class="submenu-content-container"><div class="submenu-item-heading">Web APIs</div><p class="submenu-item-description">Interfaces for building web applications</p></div></a></li><li class="apis-link-container "><a href="/en-US/docs/Mozilla/Add-ons/WebExtensions" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Web Extensions</div><p class="submenu-item-description">Developing extensions for web browsers</p></div></a></li><li class=" "><a href="/en-US/docs/Web/Accessibility" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Accessibility</div><p class="submenu-item-description">Build web projects usable for all</p></div></a></li><li class="apis-link-container desktop-only "><a href="/en-US/docs/Web" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Web Technology</div><p class="submenu-item-description">Web technology reference for developers</p></div></a></li></ul></li><li class="top-level-entry-container "><button type="button" id="learn-button" class="top-level-entry menu-toggle" aria-controls="learn-menu" aria-expanded="false">Learn</button><a href="/en-US/docs/Learn_web_development" class="top-level-entry">Learn</a><ul id="learn-menu" class="submenu learn hidden inline-submenu-lg" aria-labelledby="learn-button"><li class="apis-link-container mobile-only "><a href="/en-US/docs/Learn_web_development" class="submenu-item "><div class="submenu-icon learn"></div><div class="submenu-content-container"><div class="submenu-item-heading">Overview / MDN Learning Area</div><p class="submenu-item-description">Learn web development</p></div></a></li><li class="apis-link-container desktop-only "><a href="/en-US/docs/Learn_web_development" class="submenu-item "><div class="submenu-icon learn"></div><div class="submenu-content-container"><div class="submenu-item-heading">MDN Learning Area</div><p class="submenu-item-description">Learn web development</p></div></a></li><li class="html-link-container "><a href="/en-US/docs/Learn_web_development/Core/Structuring_content" class="submenu-item "><div class="submenu-icon html"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTML</div><p class="submenu-item-description">Learn to structure web content with HTML</p></div></a></li><li class="css-link-container "><a href="/en-US/docs/Learn_web_development/Core/Styling_basics" class="submenu-item "><div class="submenu-icon css"></div><div class="submenu-content-container"><div class="submenu-item-heading">CSS</div><p class="submenu-item-description">Learn to style content using CSS</p></div></a></li><li class="javascript-link-container "><a href="/en-US/docs/Learn_web_development/Core/Scripting" class="submenu-item "><div class="submenu-icon javascript"></div><div class="submenu-content-container"><div class="submenu-item-heading">JavaScript</div><p class="submenu-item-description">Learn to run scripts in the browser</p></div></a></li><li class=" "><a href="/en-US/docs/Learn_web_development/Core/Accessibility" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Accessibility</div><p class="submenu-item-description">Learn to make the web accessible to all</p></div></a></li></ul></li><li class="top-level-entry-container "><button type="button" id="mdn-plus-button" class="top-level-entry menu-toggle" aria-controls="mdn-plus-menu" aria-expanded="false">Plus</button><a href="/en-US/plus" class="top-level-entry">Plus</a><ul id="mdn-plus-menu" class="submenu mdn-plus hidden inline-submenu-lg" aria-labelledby="mdn-plus-button"><li class=" "><a href="/en-US/plus" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Overview</div><p class="submenu-item-description">A customized MDN experience</p></div></a></li><li class=" "><a href="/en-US/plus/ai-help" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">AI Help</div><p class="submenu-item-description">Get real-time assistance and support</p></div></a></li><li class=" "><a href="/en-US/plus/updates" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Updates</div><p class="submenu-item-description">All browser compatibility updates at a glance</p></div></a></li><li class=" "><a href="/en-US/plus/docs/features/overview" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Documentation</div><p class="submenu-item-description">Learn how to use MDN Plus</p></div></a></li><li class=" "><a href="/en-US/plus/docs/faq" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">FAQ</div><p class="submenu-item-description">Frequently asked questions about MDN Plus</p></div></a></li></ul></li><li class="top-level-entry-container "><a class="top-level-entry menu-link" href="/en-US/curriculum/">Curriculum <sup class="new">New</sup></a></li><li class="top-level-entry-container "><a class="top-level-entry menu-link" href="/en-US/blog/">Blog</a></li><li class="top-level-entry-container "><button type="button" id="tools-button" class="top-level-entry menu-toggle" aria-controls="tools-menu" aria-expanded="false">Tools</button><ul id="tools-menu" class="submenu tools hidden inline-submenu-lg" aria-labelledby="tools-button"><li class=" "><a href="/en-US/play" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">Playground</div><p class="submenu-item-description">Write, test and share your code</p></div></a></li><li class=" "><a href="/en-US/observatory" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">HTTP Observatory</div><p class="submenu-item-description">Scan a website for free</p></div></a></li><li class=" "><a href="/en-US/plus/ai-help" class="submenu-item "><div class="submenu-icon"></div><div class="submenu-content-container"><div class="submenu-item-heading">AI Help</div><p class="submenu-item-description">Get real-time assistance and support</p></div></a></li></ul></li></ul></nav><div class="header-search"><form action="/en-US/search" class="search-form search-widget" id="top-nav-search-form" role="search"><label id="top-nav-search-label" for="top-nav-search-input" class="visually-hidden">Search MDN</label><input aria-activedescendant="" aria-autocomplete="list" aria-controls="top-nav-search-menu" aria-expanded="false" aria-labelledby="top-nav-search-label" autoComplete="off" id="top-nav-search-input" role="combobox" type="search" class="search-input-field" name="q" placeholder=" " required="" value=""/><button type="button" class="button action has-icon clear-search-button"><span class="button-wrap"><span class="icon icon-cancel "></span><span class="visually-hidden">Clear search input</span></span></button><button type="submit" class="button action has-icon search-button"><span class="button-wrap"><span class="icon icon-search "></span><span class="visually-hidden">Search</span></span></button><div id="top-nav-search-menu" role="listbox" aria-labelledby="top-nav-search-label"></div></form></div><div class="theme-switcher-menu"><button type="button" class="button action has-icon theme-switcher-menu small" aria-haspopup="menu"><span class="button-wrap"><span class="icon icon-theme-os-default "></span>Theme</span></button></div><ul class="auth-container"><li><a href="/users/fxa/login/authenticate/?next=%2Fen-US%2Fdocs%2FMDN%2FCommunity%2FIssues" class="login-link" rel="nofollow">Log in</a></li><li><a href="/users/fxa/login/authenticate/?next=%2Fen-US%2Fdocs%2FMDN%2FCommunity%2FIssues" target="_self" rel="nofollow" class="button primary mdn-plus-subscribe-link"><span class="button-wrap">Sign up for free</span></a></li></ul></div></div></header><div class="article-actions-container"><div class="container"><button type="button" class="button action has-icon sidebar-button" aria-label="Expand sidebar" aria-expanded="false" aria-controls="sidebar-quicklinks"><span class="button-wrap"><span class="icon icon-sidebar "></span></span></button><nav class="breadcrumbs-container" aria-label="Breadcrumb"><ol typeof="BreadcrumbList" vocab="https://schema.org/" aria-label="breadcrumbs"><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/MDN" class="breadcrumb" property="item" typeof="WebPage"><span property="name">MDN Web Docs</span></a><meta property="position" content="1"/></li><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/MDN/Community" class="breadcrumb" property="item" typeof="WebPage"><span property="name">Resources</span></a><meta property="position" content="2"/></li><li property="itemListElement" typeof="ListItem"><a href="/en-US/docs/MDN/Community/Issues" class="breadcrumb-current-page" property="item" typeof="WebPage"><span property="name">Creating and working on issues</span></a><meta property="position" content="3"/></li></ol></nav><div class="article-actions"><button type="button" class="button action has-icon article-actions-toggle" aria-label="Article actions"><span class="button-wrap"><span class="icon icon-ellipses "></span><span class="article-actions-dialog-heading">Article Actions</span></span></button><ul class="article-actions-entries"><li class="article-actions-entry"><div class="languages-switcher-menu open-on-focus-within"><button id="languages-switcher-button" type="button" class="button action small has-icon languages-switcher-menu" aria-haspopup="menu"><span class="button-wrap"><span class="icon icon-language "></span>English (US)</span></button><div class="hidden"><ul class="submenu language-menu " aria-labelledby="language-menu-button"><li class=" "><form class="submenu-item locale-redirect-setting"><div class="group"><label class="switch"><input type="checkbox" name="locale-redirect"/><span class="slider"></span><span class="label">Remember language</span></label><a href="https://github.com/orgs/mdn/discussions/739" rel="external noopener noreferrer" target="_blank" title="Enable this setting to automatically switch to this language when it's available. (Click to learn more.)"><span class="icon icon-question-mark "></span></a></div></form></li><li class=" "><a data-locale="de" href="/de/docs/MDN/Community/Issues" class="button submenu-item"><span>Deutsch</span><span title="Diese Übersetzung ist Teil eines Experiments."><span class="icon icon-experimental "></span></span></a></li><li class=" "><a data-locale="fr" href="/fr/docs/MDN/Community/Issues" class="button submenu-item"><span>Français</span></a></li><li class=" "><a data-locale="ja" href="/ja/docs/MDN/Community/Issues" class="button submenu-item"><span>日本語</span></a></li><li class=" "><a data-locale="ru" href="/ru/docs/MDN/Community/Issues" class="button submenu-item"><span>Русский</span></a></li><li class=" "><a data-locale="zh-CN" href="/zh-CN/docs/MDN/Community/Issues" class="button submenu-item"><span>中文 (简体)</span></a></li></ul></div></div></li></ul></div></div></div></div><div class="main-wrapper"><div class="sidebar-container"><aside id="sidebar-quicklinks" class="sidebar" data-macro="mdnsidebar"><button type="button" class="button action backdrop" aria-label="Collapse sidebar"><span class="button-wrap"></span></button><nav aria-label="Related Topics" class="sidebar-inner"><header class="sidebar-actions"><section class="sidebar-filter-container"><div class="sidebar-filter "><label id="sidebar-filter-label" class="sidebar-filter-label" for="sidebar-filter-input"><span class="icon icon-filter"></span><span class="visually-hidden">Filter sidebar</span></label><input id="sidebar-filter-input" autoComplete="off" class="sidebar-filter-input-field false" type="text" placeholder="Filter" value=""/><button type="button" class="button action has-icon clear-sidebar-filter-button"><span class="button-wrap"><span class="icon icon-cancel "></span><span class="visually-hidden">Clear filter input</span></span></button></div></section></header><div class="sidebar-inner-nav"><div class="in-nav-toc"><div class="document-toc-container"><section class="document-toc"><header><h2 class="document-toc-heading">In this article</h2></header><ul class="document-toc-list"><li class="document-toc-item "><a class="document-toc-link" href="#general_guidelines_for_participation">General guidelines for participation</a></li><li class="document-toc-item "><a class="document-toc-link" href="#guidelines_for_reporting_an_issue">Guidelines for reporting an issue</a></li><li class="document-toc-item "><a class="document-toc-link" href="#guidelines_for_working_on_an_issue">Guidelines for working on an issue</a></li><li class="document-toc-item "><a class="document-toc-link" href="#guidelines_for_triaging_issues">Guidelines for triaging issues</a></li></ul></section></div></div><div class="sidebar-body"><ol><li class="section"><a href="/en-US/docs/MDN">MDN Web Docs</a></li><li><a href="/en-US/docs/MDN/Tutorials">Tutorials</a></li><li><a href="/en-US/docs/MDN/Guides">Guides</a></li><li class="toggle"><details open=""><summary>Community resources</summary><ol><li><a href="/en-US/docs/MDN/Community">Resources</a></li><li><a href="/en-US/docs/MDN/Community/Getting_started">Getting started</a></li><li><a href="/en-US/docs/MDN/Community/Our_repositories">GitHub repositories</a></li><li><a href="/en-US/docs/MDN/Community/Open_source_etiquette">Open source etiquette</a></li><li><em><a href="/en-US/docs/MDN/Community/Issues" aria-current="page">Creating and working on issues</a></em></li><li><a href="/en-US/docs/MDN/Community/Pull_requests">Pull request submission and reviews</a></li><li><a href="/en-US/docs/MDN/Community/Discussions">GitHub Discussions</a></li><li><a href="/en-US/docs/MDN/Community/Translated_content">Localization</a></li><li><a href="/en-US/docs/MDN/Community/Roles_teams">Roles and teams</a></li><li><a href="/en-US/docs/MDN/Community/Communication_channels">Communication channels</a></li><li><a href="/en-US/docs/MDN/Community/Learn_forum">Learn forum</a></li></ol></details></li><li class="toggle"><details><summary>Writing guidelines</summary><ol><li><a href="/en-US/docs/MDN/Writing_guidelines">Writing guidelines</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/What_we_write">What we write</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Writing_style_guide">Style guide</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Learning_content">Learning content guidelines</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Experimental_deprecated_obsolete">Experimental, deprecated, and obsolete</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license">Attribution and copyright licensing</a></li><li class="toggle"><details><summary>How-to guides</summary><ol><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto">Overview</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Write_a_new_entry_in_the_glossary">Add a glossary entry</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Images_media">Add media</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Creating_moving_deleting">Create, edit, move, or delete pages</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Document_a_CSS_property">Document a CSS property</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Document_an_HTTP_header">Document an HTTP header</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Document_web_errors">Document errors</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Research_technology">Research a technology</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/JSON_Structured_data">Use structured data</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Write_an_api_reference">Write an API reference</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN">Write in Markdown</a></li></ol></details></li><li class="toggle"><details><summary>Page structures</summary><ol><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures">Overview</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Banners_and_notices">Banners and notices</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Code_examples">Code examples</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Compatibility_tables">Compatibility tables and the browser compatibility data repository (BCD)</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Feature_status">Feature status</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Links">Link macros</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Live_samples">Live examples</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types">Page types</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Sidebars">Sidebars</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Specification_tables">Specification tables</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Syntax_sections">Syntax sections</a></li><li><a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Macros">Using macros</a></li></ol></details></li></ol></details></li></ol></div></div><section class="place side"></section></nav></aside><div class="toc-container"><aside class="toc"><nav><div class="document-toc-container"><section class="document-toc"><header><h2 class="document-toc-heading">In this article</h2></header><ul class="document-toc-list"><li class="document-toc-item "><a class="document-toc-link" href="#general_guidelines_for_participation">General guidelines for participation</a></li><li class="document-toc-item "><a class="document-toc-link" href="#guidelines_for_reporting_an_issue">Guidelines for reporting an issue</a></li><li class="document-toc-item "><a class="document-toc-link" href="#guidelines_for_working_on_an_issue">Guidelines for working on an issue</a></li><li class="document-toc-item "><a class="document-toc-link" href="#guidelines_for_triaging_issues">Guidelines for triaging issues</a></li></ul></section></div></nav></aside><section class="place side"></section></div></div><main id="content" class="main-content "><article class="main-page-content" lang="en-US"><header><h1>Creating and working on issues</h1></header><div class="section-content"><p>As a contributor, you can <a href="#guidelines_for_reporting_an_issue">report</a> and <a href="#guidelines_for_working_on_an_issue">work</a> on issues. After you report an issue, the issue gets triaged. Issue <a href="#guidelines_for_triaging_issues">triaging</a> is typically done by people assigned the role of a maintainer or an owner.</p></div><section aria-labelledby="general_guidelines_for_participation"><h2 id="general_guidelines_for_participation"><a href="#general_guidelines_for_participation">General guidelines for participation</a></h2><div class="section-content"><p>While reporting an issue or participating in a conversation in an issue, always ensure that your inputs are contributing to the overall progress of the project. Consider whether the issues you open and your comments in an issue are constructive and on topic and are not just adding noise.</p> <p>Do the following:</p> <ul> <li>Before filing an issue, consider if you need to <a href="/en-US/docs/MDN/Community/Communication_channels#chat_rooms">discuss</a> it with the staff/community. Use discussions to gain different viewpoints and to converge on an agreed-upon course of action. This helps to keep issues focused and productive.</li> <li>After filing an issue, try to fix the problem yourself. Read our <a href="https://github.com/mdn/content/blob/main/CONTRIBUTING.md" class="external" target="_blank">contribution guide</a> to learn more.</li> <li>If you have a question, you can ask it in the <a href="/en-US/docs/MDN/Community/Communication_channels#chat_rooms">MDN Web Docs chat rooms</a> instead of filing an issue.</li> </ul> <p>Avoid doing the following:</p> <ul> <li>Complicating issues by trying to discuss multiple topics or by making off-topic comments.</li> <li>Opening lots of issues asking vague questions.</li> <li>Asking questions without trying to solve the problem yourself first.</li> </ul></div></section><section aria-labelledby="guidelines_for_reporting_an_issue"><h2 id="guidelines_for_reporting_an_issue"><a href="#guidelines_for_reporting_an_issue">Guidelines for reporting an issue</a></h2><div class="section-content"><p><a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues" class="external" target="_blank">Issues</a> are used to track bugs. An issue must be a single actionable task or a collection of related actionable tasks and must have a clear outcome.</p></div></section><section aria-labelledby="before_filing_an_issue"><h3 id="before_filing_an_issue"><a href="#before_filing_an_issue">Before filing an issue</a></h3><div class="section-content"><p>If you think you've found a bug with the content on MDN Web Docs or with the look and feel of the website, search the current open issues in the <a href="/en-US/docs/MDN/Community/Our_repositories">relevant repository</a> and make sure nobody else has reported the issue.</p></div></section><section aria-labelledby="reporting_an_issue"><h3 id="reporting_an_issue"><a href="#reporting_an_issue">Reporting an issue</a></h3><div class="section-content"><ul> <li> <p>Depending on the type of problem you've discovered, report it by filing an issue on one of the followings:</p> <ul> <li><a href="https://github.com/mdn/content/issues/new/choose" class="external" target="_blank">documentation</a></li> <li><a href="https://github.com/mdn/translated-content/issues/new/choose" class="external" target="_blank">translation</a></li> <li>the website's <a href="https://github.com/mdn/yari/issues/new/choose" class="external" target="_blank">look and feel</a></li> <li>the "Try it" <a href="https://github.com/mdn/interactive-examples/issues/new/choose" class="external" target="_blank">interactive example</a> section</li> <li><a href="https://github.com/mdn/dom-examples/issues" class="external" target="_blank">DOM examples</a></li> <li><a href="https://github.com/mdn/learning-area/issues" class="external" target="_blank">Learning area</a></li> <li>the <a href="https://github.com/mdn/browser-compat-data/issues/new/choose" class="external" target="_blank">browser compatibility</a> information</li> </ul> </li> <li> <p>Choose the appropriate category to report the issue. For example, to report a content bug, use the <a href="https://github.com/mdn/content/issues/new?assignees=&labels=needs+triage&template=content-bug.yml" class="external" target="_blank">Content issue</a> template in the <code>mdn/content</code> repository.</p> </li> <li> <p>Provide sufficient information while reporting the issue:</p> <ul> <li> <p><strong>Issue title</strong> must convey succinctly the <em>required action</em>.</p> </li> <li> <p><strong>Issue description</strong> must clearly describe the bug and the action required to resolve the issue. It must also list the task or sub-tasks to be completed to resolve the issue. Some other guidelines include:</p> <ul> <li>Use the description field to indicate the status of the task or sub-tasks by using checklists.</li> <li>Update the status of a task in the issue description instead of commenting on the issue. Use <a href="https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists" class="external" target="_blank">task lists</a> in the description if an issue has multiple parts. This helps others who may otherwise need to scroll through comments on the issue to determine the status of various tasks.</li> <li>Comments in an issue should be limited to details or context that help resolve the issue.</li> </ul> </li> </ul> </li> <li> <p>If the information you provide in the issue is incomplete, then you might be contacted later during the <a href="#review_the_issue_for_completeness_of_information">issue triaging process</a>.</p> </li> <li> <p>If you find yourself in one of the following situations, move the conversation to <a href="https://github.com/orgs/mdn/discussions" class="external" target="_blank">MDN's discussion on GitHub</a>:</p> <ul> <li>A discussion needs to take place to clarify an issue.</li> <li>A discussion begins after opening the issue.</li> <li>The issue has no clear consensus on its resolution.</li> <li>The requirements for completing the task expand while it's being resolved or the work is unclear.</li> </ul> </li> <li> <p>For minor and small bugs, you can <a href="#fixing_issues_yourself">make the changes yourself</a> and submit a pull request.</p> </li> </ul></div></section><section aria-labelledby="creating_a_task_list_issue"><h3 id="creating_a_task_list_issue"><a href="#creating_a_task_list_issue">Creating a task list issue</a></h3><div class="section-content"><p>If the issue you're opening is not to report a bug but to perform a series of tasks, you can create the issue as a <a href="https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists" class="external" target="_blank">task list</a>. Explain the context or reason for performing the tasks in the description. Ensure that you list all the actionable tasks as a checklist.</p> <p>For example:</p> <div class="code-example"><div class="example-header"><span class="language-name">markdown</span></div><pre class="brush: markdown notranslate"><code>// Issue title Ensure sections follow the order defined in the CSS property template ### Description The CSS property page template is defined [here](/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types/CSS_property_page_template). The task list in this issue will be used to compare the documented CSS properties with the template and track changes to the property pages for compliance. ### List of pages checked - [x] [accent-color](/en-US/docs/Web/CSS/accent-color) - checked, okay - [ ] [backdrop-filter](/en-US/docs/Web/CSS/backdrop-filter) - [ ] [letter-spacing](/en-US/docs/Web/CSS/letter-spacing) - open pull request to move `Accessibility concerns` and `Internationalization concerns` sections before the `Specifications` section. </code></pre></div></div></section><section aria-labelledby="guidelines_for_working_on_an_issue"><h2 id="guidelines_for_working_on_an_issue"><a href="#guidelines_for_working_on_an_issue">Guidelines for working on an issue</a></h2><div class="section-content"><p>Remember that if you take on an issue, the expectation is for the work to be completed in a timely manner. If you're not able to make any progress for a week after being assigned or can no longer complete the required task, leave a comment and unassign yourself from the issue.</p> <p>These are the general steps for working on an issue:</p> <ol> <li> <p><strong>Find an issue:</strong> If you're looking to contribute, search for issues with <a href="#set_other_labels"><code>good first issue</code>, <code>help wanted</code></a> or <a href="#set_a_priority_label"><code>p3</code></a> label. Most repositories have issues with these labels. You are welcome to browse and pick an issue that is suitable for your skill set. Another useful place to look for issues to work on is the <a href="https://github.com/orgs/mdn/projects/25" class="external" target="_blank">MDN Contributors Task Board</a>. This project view lists open issues from multiple repositories. You can filter the list based on the topics (<code>Labels</code> column) you're interested in. See the description of some of the <a href="#set_other_labels">labels</a> that get applied during the issue triage process.</p> <div class="notecard note"> <p><strong>Note:</strong> An issue with the <code>needs triage</code> label indicates that the MDN Web Docs core team has not reviewed the issue yet, and you shouldn't begin work on it.</p> </div> </li> <li> <p><strong>Assign the issue to yourself:</strong> After finding an issue you'd like to work on, make sure that the issue is not assigned to anybody else. Add a comment saying you would like to work on the issue, and if you are able to, <a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users#assigning-an-individual-issue-or-pull-request" class="external" target="_blank">assign the issue to yourself</a>.</p> </li> <li> <p><strong>Do the research:</strong> Most issues need some investigation before work can start.</p> <ul> <li>Scope out the work that needs to be done. If you need to ask questions, ask them in the <a href="/en-US/docs/MDN/Community/Communication_channels#chat_rooms">MDN Web Docs chat rooms</a>.</li> <li>If the issue is well-described, and the work is pretty obvious, go ahead and do it.</li> <li>If the issue is not well-described, and/or you are not sure what is needed, feel free to @mention the poster and ask for more information.</li> </ul> </li> <li> <p><strong>Make the changes:</strong> Fork and branch the repository. Do your work and open a <a href="/en-US/docs/MDN/Community/Pull_requests">pull request</a> in the repository. <a href="https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue" class="external" target="_blank">Reference the issue</a> in the pull request description. Depending on the files you've updated in the pull request, a reviewer will be assigned to your pull request automatically. (Teams per topic area are defined in the <a href="https://github.com/mdn/content/blob/main/.github/CODEOWNERS" class="external" target="_blank">CODEOWNERS</a> file).</p> <p>After opening the pull request, if you find you no longer have the time to make changes or incorporate review feedback, let the team know as soon as possible in a comment in the pull request. This will help the team assign another interested contributor to complete the work on the pull request and close the linked issue.</p> </li> <li> <p>After your pull request has been reviewed and merged, you can mark the linked issue as closed. If you opened the pull request with <code>Fixes #<issue></code> verbiage, the issue will be closed automatically when the pull request is merged.</p> </li> </ol></div></section><section aria-labelledby="fixing_issues_yourself"><h3 id="fixing_issues_yourself"><a href="#fixing_issues_yourself">Fixing issues yourself</a></h3><div class="section-content"><p>If you spot a bug — whether it's a problem with the website's look and feel or an error in documentation — you can try to fix it yourself. Learn how you can contribute by going through our <a href="https://github.com/mdn/content/blob/main/CONTRIBUTING.md" class="external" target="_blank">contribution guide</a>.</p> <p>If the bug is small, such as a typo or a minor sentence improvement, or involves an uncontroversial fix, submit a pull request with the changes.</p> <p>For all other type of bugs, begin by <a href="#guidelines_for_reporting_an_issue">opening the issue</a>. Add a comment about your intent to work on the issue and if possible, describe your proposed solution or steps to fix the issue. Wait for the issue to be triaged, so that the MDN Web Docs team can verify that the issue is legit and approves your proposed solution.</p> <div class="notecard note"> <p><strong>Note:</strong> If you open a pull request before the issue has been triaged, your time and effort might go waste if the linked issue is deemed invalid or the solution does not match the one expected by the MDN Web Docs team. After the issue is triaged, assign the issue to yourself.</p> </div> <p>Using the <a href="#guidelines_for_working_on_an_issue">guidelines on working on an issue</a>, try to fix the problem by updating the appropriate source, such as:</p> <ul> <li>The MDN Web Docs content (in English) in the <a href="https://github.com/mdn/content" class="external" target="_blank">content</a> repository</li> <li>The MDN Web Docs translated content in the <a href="https://github.com/mdn/translated-content" class="external" target="_blank">translated-content</a> repository</li> <li>The MDN Web Docs website look and feel in the <a href="https://github.com/mdn/yari" class="external" target="_blank">yari</a> repository</li> </ul> <p>Each repository includes useful information to guide you on how to contribute.</p></div></section><section aria-labelledby="guidelines_for_triaging_issues"><h2 id="guidelines_for_triaging_issues"><a href="#guidelines_for_triaging_issues">Guidelines for triaging issues</a></h2><div class="section-content"><p>If you are a maintainer or an owner in the MDN Web Docs GitHub organization, you are responsible for triaging issues in one or more MDN Web Docs repository.</p> <p>The overall process for triaging includes some <a href="#general_triaging_tasks">general</a> and some <a href="#issue-specific_triaging_tasks">issue-specific tasks</a>.</p></div></section><section aria-labelledby="general_triaging_tasks"><h3 id="general_triaging_tasks"><a href="#general_triaging_tasks">General triaging tasks</a></h3><div class="section-content"><ul> <li> <p>When an issue is opened, the <code>needs triage</code> label is set on the issue automatically. You can search for this label to look for issues that <a href="#issue-specific_triaging_tasks">need to be triaged</a>. Contributors or anybody else should not work on the issue until the issue has been triaged. (Triagers should remember to remove the <code>needs triage</code> label after triaging the issue.)</p> </li> <li> <p>In the <a href="https://github.com/mdn/content/issues" class="external" target="_blank">mdn/content repository</a>, an additional <code>Content:</code> label, such as <code>Content:CSS</code> or <code>Content:WebAPI</code>, is set on the issue automatically. This gets set based on the MDN URL mentioned in the issue. You can use the content-specific label to look for issues to be triaged in your specific topic area.</p> </li> <li> <p>If an issue concerns an active, non-en-US locale, set the appropriate label, such as <code>l10n-fr</code>, <code>l10n-zh</code>, or <code>l10n-ja</code>. The teams for those locales will pick these issues up and triage them.</p> </li> <li> <p>You don't need to actively triage issues all the time. Set aside time, say 30 minutes every week, to triage issues on a regular basis in your area of responsibility. Triaging doesn't have to be done as part of a synchronous meeting or even at the same time as everyone else, but it should be done regularly to make sure that the backlog of untriaged bugs doesn't get too high.</p> </li> <li> <p>Apart from triaging incoming issues every week, review the list of old bugs to see if there are any that are stalled, need closing, or are no longer relevant. The <code>idle</code> label is automatically set on issues that have had no activity for 30 days.</p> <ul> <li>Check assigned issues that are still open to see if the assignee is making progress. If there is no progress after a week of being assigned, ask them if they still have time to work on the issue. If another week passes by without any progress, unassign them and leave a comment indicating that you're making the issue available for other interested contributors.</li> <li>If a pull request has been opened to fix the issue but has not been reviewed for a week, give the reviewer a gentle ping to ask if they can get to it.</li> <li>If a pull request to fix the issue is waiting on review comments to be addressed after a week, then ask the author if they can respond to their review. If another week goes by, either fix the review comments yourself if you have time, or close the pull request and unassign the related issue.</li> </ul> </li> </ul></div></section><section aria-labelledby="issue-specific_triaging_tasks"><h3 id="issue-specific_triaging_tasks"><a href="#issue-specific_triaging_tasks">Issue-specific triaging tasks</a></h3><div class="section-content"><p>These are the guidelines to follow while triaging each issue.</p> <h4 id="review_if_the_issue_is_valid">Review if the issue is valid</h4> <p>These are some of the things to keep in mind while reviewing the validity of an issue:</p> <ul> <li>Check if the issue raised is valid and if the fix will improve the content for the readers and the website.</li> <li>Evaluate if the impact of the fix will be small or site-wide.</li> <li>Evaluate if the fix for the issue will need a discussion first, in which case, point the author to open a <a href="https://github.com/orgs/mdn/discussions" class="external" target="_blank">discussion</a> instead.</li> <li>Check if the issue complies with our <a href="/en-US/docs/MDN/Writing_guidelines/Writing_style_guide">writing guidelines</a> and <a href="/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types">templates</a>.</li> <li>Check whether suggestions for adding links comply with our <a href="/en-US/docs/MDN/Writing_guidelines/Writing_style_guide#external_links">external links policy</a>.</li> </ul> <h4 id="review_the_issue_for_completeness_of_information">Review the issue for completeness of information</h4> <p>Review each issue against the following checklist to ensure that the issue contains the described information for someone to start working on the bug:</p> <ul> <li>URL of the MDN Web Docs page with the problem or URL of an example MDN Web Docs page if the problem exists on multiple pages</li> <li>The specific heading or section on the MDN Web Docs page where the problem was found</li> <li>A clear description of the incorrect, unhelpful, incomplete, or missing information</li> </ul> <p>If any of the above information is not present, then you should ask the author of the issue to provide these details, and add the <code>needs info</code> label to the issue. Resume triaging the issue only after those details have been provided (after which, you can remove the <code>needs info</code> label). It is okay to wait for up to a week to get a response from the author.</p> <h4 id="set_a_priority_label">Set a priority label</h4> <p>For each bug, set a priority label based on the severity of the issue to help people who want to work on the most important issues or areas.</p> <ul> <li> <p>Critical issue: This type of issue needs to be fixed as soon as possible, regardless of where it appears on the site. This type of issue could damage MDN's reputation severely and/or harm users. Examples of this issue include an incorrect code snippet, which if used in production, could create a severe security problem and undesirable content such as malware, profanity, pornography, hate speech, or links to such content.</p> <ul> <li>Label: <code>p0</code> (will be addressed immediately)</li> </ul> </li> <li> <p>Major issue: This type of issue could severely affect a page's usefulness. For example, a significant amount of out-of-date information, a complex and important code example that doesn't work, a significant amount of prose that is badly written and hard to understand, or a large number of broken links.</p> <ul> <li>Labels: <code>p1</code> (will be addressed soon) and <code>p2</code> (will be addressed soon, but higher priority items will take precedence)</li> </ul> </li> <li> <p>Minor issue: This is a type of improvement issue that can make the existing content better but does not affect learning or only has a minor effect on learning. Since these types of issues are not actively planned for, help from contributors to fix these issues is welcome and much appreciated. Fixing some of these issues can also provide the necessary practice to beginner contributors who are starting to get familiar with the contribution process. Examples include typos, bad grammar, a broken link, a small amount of out-of-date information or badly-written prose, or a code snippet that doesn't work.</p> <ul> <li>Labels: <code>p3</code> (no visibility when the issue will be addressed)</li> </ul> </li> </ul> <p>In general, critical issues should be fixed immediately and are most likely handled by MDN Web Docs staff and peers.</p> <h4 id="add_helpful_information">Add helpful information</h4> <p>If possible, add information that can help contributors to fix the issue. The information can be in the form of steps, general approach, links to other similar fixed issues, or reading resources. A well-laid out plan or steps is especially required in issues that are labeled <code>good first issue</code> and can help ramp up new contributors quickly. You can time-box this task to 5-10 minutes.</p> <p>For example, as a triager, you can add the following information to the issue you are triaging:</p> <div class="code-example"><div class="example-header"><span class="language-name">md</span></div><pre class="brush: md notranslate"><code>To whoever fixes this issue, it looks like the following is needed: - Update the first paragraph below heading X to correct the problem with Y - Add a description of X - Update the compatibility data at Link-X </code></pre></div> <h4 id="set_other_labels">Set other labels</h4> <p>Next, set the following labels as appropriate:</p> <ul> <li> <p><code>effort: small</code>, <code>effort: medium</code>, <code>effort: large</code>: Some contributors like to search for bugs based on the time and effort that will be needed to fix the bug. So where possible, you should try to provide an estimate of the required effort.</p> </li> <li> <p><code>good first issue</code>: Set this label on the issue if the fix for the issue is really simple and if fixing the issue would provide good practice for a newcomer who is getting used to the process.</p> </li> <li> <p><code>help wanted</code>: Set this label if the issue requires help from someone who knows about or is familiar with the topic. This is a popular label and some contributors use it to search for issues to work on in open source projects in their areas of familiarity or expertise.</p> </li> <li> <p><code>broken link external</code>: Set this label if the issue involves a broken link to an external page.</p> </li> <li> <p><code>document not written</code>: Set this label if the issue involves a necessary document that has not been written yet, usually because a link points to it.</p> </li> <li> <p><code>needs content update</code>: Set this label if the issue fix in another repository will need an equivalent fix in the <code>mdn/content</code> repository.</p> <div class="notecard note"> <p><strong>Note:</strong> After the triage process is complete, remove the <code>needs triage</code> label.</p> </div> </li> </ul></div></section></article><aside class="article-footer"><div class="article-footer-inner"><div class="svg-container"><svg xmlns="http://www.w3.org/2000/svg" width="162" height="162" viewBox="0 0 162 162" fill="none" role="none"><mask id="b" fill="#fff"><path d="M97.203 47.04c8.113-7.886 18.004-13.871 28.906-17.492a78 78 0 0 1 33.969-3.39c11.443 1.39 22.401 5.295 32.024 11.411s17.656 14.28 23.476 23.86c5.819 9.579 9.269 20.318 10.083 31.385a69.85 69.85 0 0 1-5.387 32.44c-4.358 10.272-11.115 19.443-19.747 26.801-8.632 7.359-18.908 12.709-30.034 15.637l-6.17-21.698c7.666-2.017 14.746-5.703 20.694-10.773 5.948-5.071 10.603-11.389 13.606-18.467a48.14 48.14 0 0 0 3.712-22.352c-.561-7.625-2.938-15.025-6.948-21.625s-9.544-12.226-16.175-16.44-14.181-6.904-22.065-7.863a53.75 53.75 0 0 0-23.405 2.336c-7.513 2.495-14.327 6.62-19.918 12.053z"></path></mask><path stroke="url(#a)" stroke-dasharray="6, 6" stroke-width="2" d="M97.203 47.04c8.113-7.886 18.004-13.871 28.906-17.492a78 78 0 0 1 33.969-3.39c11.443 1.39 22.401 5.295 32.024 11.411s17.656 14.28 23.476 23.86c5.819 9.579 9.269 20.318 10.083 31.385a69.85 69.85 0 0 1-5.387 32.44c-4.358 10.272-11.115 19.443-19.747 26.801-8.632 7.359-18.908 12.709-30.034 15.637l-6.17-21.698c7.666-2.017 14.746-5.703 20.694-10.773 5.948-5.071 10.603-11.389 13.606-18.467a48.14 48.14 0 0 0 3.712-22.352c-.561-7.625-2.938-15.025-6.948-21.625s-9.544-12.226-16.175-16.44-14.181-6.904-22.065-7.863a53.75 53.75 0 0 0-23.405 2.336c-7.513 2.495-14.327 6.62-19.918 12.053z" mask="url(#b)" style="stroke:url(#a)" transform="translate(-63.992 -25.587)"></path><ellipse cx="8.066" cy="111.597" fill="var(--background-tertiary)" rx="53.677" ry="53.699" transform="matrix(.71707 -.697 .7243 .6895 0 0)"></ellipse><g clip-path="url(#c)" transform="translate(-63.992 -25.587)"><path fill="#9abff5" d="m144.256 137.379 32.906 12.434a4.41 4.41 0 0 1 2.559 5.667l-9.326 24.679a4.41 4.41 0 0 1-5.667 2.559l-8.226-3.108-2.332 6.17c-.466 1.233-.375 1.883-1.609 1.417l-2.253-.527c-.411-.155-.95-.594-1.206-1.161l-4.734-10.484-12.545-4.741a4.41 4.41 0 0 1-2.559-5.667l9.325-24.679a4.41 4.41 0 0 1 5.667-2.559m9.961 29.617 8.227 3.108 3.264-8.638-.498-6.768-4.113-1.555.548 7.258-4.319-1.632zm-12.339-4.663 8.226 3.108 3.264-8.637-.498-6.769-4.113-1.554.548 7.257-4.319-1.632z"></path></g><g clip-path="url(#d)" transform="translate(-63.992 -25.587)"><path fill="#81b0f3" d="M135.35 60.136 86.67 41.654c-3.346-1.27-7.124.428-8.394 3.775L64.414 81.938c-1.27 3.347.428 7.125 3.774 8.395l12.17 4.62-3.465 9.128c-.693 1.826-1.432 2.457.394 3.15l3.014 1.625c.609.231 1.637.274 2.477-.104l15.53-6.983 18.56 7.047c3.346 1.27 7.124-.428 8.395-3.775l13.862-36.51c1.27-3.346-.428-7.124-3.775-8.395M95.261 83.207l-12.17-4.62 4.852-12.779 7.19-7.017 6.085 2.31-7.725 7.51 6.389 2.426zm18.255 6.93-12.17-4.62 4.852-12.778 7.189-7.017 6.085 2.31-7.725 7.51 6.39 2.426z"></path></g><defs><clipPath id="c"><path fill="#fff" d="m198.638 146.586-65.056-24.583-24.583 65.057 65.056 24.582z"></path></clipPath><clipPath id="d"><path fill="#fff" d="m66.438 14.055 96.242 36.54-36.54 96.243-96.243-36.54z"></path></clipPath><linearGradient id="a" x1="97.203" x2="199.995" y1="47.04" y2="152.793" gradientUnits="userSpaceOnUse"><stop stop-color="#086DFC"></stop><stop offset="0.246" stop-color="#2C81FA"></stop><stop offset="0.516" stop-color="#5497F8"></stop><stop offset="0.821" stop-color="#80B0F6"></stop><stop offset="1" stop-color="#9ABFF5"></stop></linearGradient></defs></svg></div><h2>Help improve MDN</h2><fieldset class="feedback"><label>Was this page helpful to you?</label><div class="button-container"><button type="button" class="button primary has-icon yes"><span class="button-wrap"><span class="icon icon-thumbs-up "></span>Yes</span></button><button type="button" class="button primary has-icon no"><span class="button-wrap"><span class="icon icon-thumbs-down "></span>No</span></button></div></fieldset><a class="contribute" href="https://github.com/mdn/content/blob/main/CONTRIBUTING.md" title="This will take you to our contribution guidelines on GitHub." target="_blank" rel="noopener noreferrer">Learn how to contribute</a>.<p class="last-modified-date">This page was last modified on <time dateTime="2025-01-31T16:22:51.000Z">Jan 31, 2025</time> by <a href="/en-US/docs/MDN/Community/Issues/contributors.txt" rel="nofollow">MDN contributors</a>.</p><div id="on-github" class="on-github"><a href="https://github.com/mdn/content/blob/main/files/en-us/mdn/community/issues/index.md?plain=1" title="Folder: en-us/mdn/community/issues (Opens in a new tab)" target="_blank" rel="noopener noreferrer">View this page on GitHub</a> • <a href="https://github.com/mdn/content/issues/new?template=page-report.yml&mdn-url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FMDN%2FCommunity%2FIssues&metadata=%3C%21--+Do+not+make+changes+below+this+line+--%3E%0A%3Cdetails%3E%0A%3Csummary%3EPage+report+details%3C%2Fsummary%3E%0A%0A*+Folder%3A+%60en-us%2Fmdn%2Fcommunity%2Fissues%60%0A*+MDN+URL%3A+https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FMDN%2FCommunity%2FIssues%0A*+GitHub+URL%3A+https%3A%2F%2Fgithub.com%2Fmdn%2Fcontent%2Fblob%2Fmain%2Ffiles%2Fen-us%2Fmdn%2Fcommunity%2Fissues%2Findex.md%0A*+Last+commit%3A+https%3A%2F%2Fgithub.com%2Fmdn%2Fcontent%2Fcommit%2F719645a32546d9e514ac530a5eb66aa4c26d4f51%0A*+Document+last+modified%3A+2025-01-31T16%3A22%3A51.000Z%0A%0A%3C%2Fdetails%3E" title="This will take you to GitHub to file a new issue." target="_blank" rel="noopener noreferrer">Report a problem with this content</a></div></div></aside></main></div></div><footer id="nav-footer" class="page-footer"><div class="page-footer-grid"><div class="page-footer-logo-col"><a href="/" class="mdn-footer-logo" aria-label="MDN homepage"><svg width="48" height="17" viewBox="0 0 48 17" fill="none" xmlns="http://www.w3.org/2000/svg"><title id="mdn-footer-logo-svg">MDN logo</title><path d="M20.04 16.512H15.504V10.416C15.504 9.488 15.344 8.824 15.024 8.424C14.72 8.024 14.264 7.824 13.656 7.824C12.92 7.824 12.384 8.064 12.048 8.544C11.728 9.024 11.568 9.64 11.568 10.392V14.184H13.008V16.512H8.472V10.416C8.472 9.488 8.312 8.824 7.992 8.424C7.688 8.024 7.232 7.824 6.624 7.824C5.872 7.824 5.336 8.064 5.016 8.544C4.696 9.024 4.536 9.64 4.536 10.392V14.184H6.6V16.512H0V14.184H1.44V8.04H0.024V5.688H4.536V7.32C5.224 6.088 6.32 5.472 7.824 5.472C8.608 5.472 9.328 5.664 9.984 6.048C10.64 6.432 11.096 7.016 11.352 7.8C11.992 6.248 13.168 5.472 14.88 5.472C15.856 5.472 16.72 5.776 17.472 6.384C18.224 6.992 18.6 7.936 18.6 9.216V14.184H20.04V16.512Z" fill="currentColor"></path><path d="M33.6714 16.512H29.1354V14.496C28.8314 15.12 28.3834 15.656 27.7914 16.104C27.1994 16.536 26.4154 16.752 25.4394 16.752C24.0154 16.752 22.8954 16.264 22.0794 15.288C21.2634 14.312 20.8554 12.984 20.8554 11.304C20.8554 9.688 21.2554 8.312 22.0554 7.176C22.8554 6.04 24.0634 5.472 25.6794 5.472C26.5594 5.472 27.2794 5.648 27.8394 6C28.3994 6.352 28.8314 6.8 29.1354 7.344V2.352H26.9754V0H32.2314V14.184H33.6714V16.512ZM29.1354 11.04V10.776C29.1354 9.88 28.8954 9.184 28.4154 8.688C27.9514 8.176 27.3674 7.92 26.6634 7.92C25.9754 7.92 25.3674 8.176 24.8394 8.688C24.3274 9.2 24.0714 10.008 24.0714 11.112C24.0714 12.152 24.3114 12.944 24.7914 13.488C25.2714 14.032 25.8394 14.304 26.4954 14.304C27.3114 14.304 27.9514 13.96 28.4154 13.272C28.8954 12.584 29.1354 11.84 29.1354 11.04Z" fill="currentColor"></path><path d="M47.9589 16.512H41.9829V14.184H43.4229V10.416C43.4229 9.488 43.2629 8.824 42.9429 8.424C42.6389 8.024 42.1829 7.824 41.5749 7.824C40.8389 7.824 40.2709 8.056 39.8709 8.52C39.4709 8.968 39.2629 9.56 39.2469 10.296V14.184H40.6869V16.512H34.7109V14.184H36.1509V8.04H34.5909V5.688H39.2469V7.344C39.9669 6.096 41.1269 5.472 42.7269 5.472C43.7509 5.472 44.6389 5.776 45.3909 6.384C46.1429 6.992 46.5189 7.936 46.5189 9.216V14.184H47.9589V16.512Z" fill="currentColor"></path></svg></a><p>Your blueprint for a better internet.</p><ul class="social-icons"><li><a href="https://mastodon.social/@mdn" target="_blank" rel="me noopener noreferrer"><span class="icon icon-mastodon"></span><span class="visually-hidden">MDN on Mastodon</span></a></li><li><a href="https://twitter.com/mozdevnet" target="_blank" rel="noopener noreferrer"><span class="icon icon-twitter-x"></span><span class="visually-hidden">MDN on X (formerly Twitter)</span></a></li><li><a href="https://github.com/mdn/" target="_blank" rel="noopener noreferrer"><span class="icon icon-github-mark-small"></span><span class="visually-hidden">MDN on GitHub</span></a></li><li><a href="/en-US/blog/rss.xml" target="_blank"><span class="icon icon-feed"></span><span class="visually-hidden">MDN Blog RSS Feed</span></a></li></ul></div><div class="page-footer-nav-col-1"><h2 class="footer-nav-heading">MDN</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a href="/en-US/about">About</a></li><li class="footer-nav-item"><a href="/en-US/blog/">Blog</a></li><li class="footer-nav-item"><a href="https://www.mozilla.org/en-US/careers/listings/?team=ProdOps" target="_blank" rel="noopener noreferrer">Careers</a></li><li class="footer-nav-item"><a href="/en-US/advertising">Advertise with us</a></li></ul></div><div class="page-footer-nav-col-2"><h2 class="footer-nav-heading">Support</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a class="footer-nav-link" href="https://support.mozilla.org/products/mdn-plus">Product help</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/docs/MDN/Community/Issues">Report an issue</a></li></ul></div><div class="page-footer-nav-col-3"><h2 class="footer-nav-heading">Our communities</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/community">MDN Community</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="https://discourse.mozilla.org/c/mdn/236" target="_blank" rel="noopener noreferrer">MDN Forum</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/discord" target="_blank" rel="noopener noreferrer">MDN Chat</a></li></ul></div><div class="page-footer-nav-col-4"><h2 class="footer-nav-heading">Developers</h2><ul class="footer-nav-list"><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/docs/Web">Web Technologies</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/docs/Learn">Learn Web Development</a></li><li class="footer-nav-item"><a class="footer-nav-link" href="/en-US/plus">MDN Plus</a></li><li class="footer-nav-item"><a href="https://hacks.mozilla.org/" target="_blank" rel="noopener noreferrer">Hacks Blog</a></li></ul></div><div class="page-footer-moz"><a href="https://www.mozilla.org/" class="footer-moz-logo-link" target="_blank" rel="noopener noreferrer"><svg xmlns="http://www.w3.org/2000/svg" width="137" height="32" fill="none" viewBox="0 0 267.431 62.607"><path fill="currentColor" d="m13.913 23.056 5.33 25.356h2.195l5.33-25.356h14.267v38.976h-7.578V29.694h-2.194l-7.264 32.337h-7.343L9.418 29.694H7.223v32.337H-.354V23.056Zm47.137 9.123c9.12 0 14.423 5.385 14.423 15.214s-5.33 15.214-14.423 15.214c-9.12 0-14.423-5.385-14.423-15.214 0-9.855 5.304-15.214 14.423-15.214m0 24.363c4.285 0 6.428-2.196 6.428-7.032v-4.287c0-4.836-2.143-7.032-6.428-7.032s-6.428 2.196-6.428 7.032v4.287c0 4.836 2.143 7.032 6.428 7.032m18.473-.157 15.47-18.01h-15.26v-5.647h24.352v5.646L88.616 56.385h15.704v5.646H79.523Zm29.318-23.657h11.183V62.03h-7.578V38.375h-3.632v-5.646zm3.605-9.672h7.578v5.646h-7.578zm13.17 0h11.21v38.976h-7.578v-33.33h-3.632zm16.801 0H153.6v38.976h-7.577v-33.33h-3.632v-5.646zm29.03 9.123c4.442 0 7.394 2.143 8.231 5.881h2.194v-5.332h9.276v5.646h-3.632v18.011h3.632v5.646h-4.442c-3.135 0-4.834-1.699-4.834-4.836V56.7h-2.194c-.81 3.738-3.789 5.881-8.23 5.881-6.978 0-11.916-5.829-11.916-15.214 0-9.384 4.938-15.187 11.915-15.187m2.3 24.363c4.284 0 6.192-2.196 6.192-7.032v-4.287c0-4.836-1.908-7.032-6.193-7.032-4.18 0-6.193 2.196-6.193 7.032v4.287c0 4.836 2.012 7.032 6.193 7.032m48.34 5.489h-7.577V0h7.577zm6.585-29.643h32.165v-2.196l-21.295-7.634v-6.143l21.295-7.633V6.588h-25.345V0h32.165v12.522l-17.35 5.881V20.6l17.35 5.882v12.521h-38.985zm0-25.801h6.794v6.796h-6.794z"></path></svg></a><ul class="footer-moz-list"><li class="footer-moz-item"><a href="https://www.mozilla.org/privacy/websites/" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Website Privacy Notice</a></li><li class="footer-moz-item"><a href="https://www.mozilla.org/privacy/websites/#cookies" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Cookies</a></li><li class="footer-moz-item"><a href="https://www.mozilla.org/about/legal/terms/mozilla" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Legal</a></li><li class="footer-moz-item"><a href="https://www.mozilla.org/about/governance/policies/participation/" class="footer-moz-link" target="_blank" rel="noopener noreferrer">Community Participation Guidelines</a></li></ul></div><div class="page-footer-legal"><p id="license" class="page-footer-legal-text">Visit <a href="https://www.mozilla.org" target="_blank" rel="noopener noreferrer">Mozilla Corporation’s</a> not-for-profit parent, the <a target="_blank" rel="noopener noreferrer" href="https://foundation.mozilla.org/">Mozilla Foundation</a>.<br/>Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under <a href="/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license">a Creative Commons license</a>.</p></div></div></footer></div><script type="application/json" id="hydration">{"url":"/en-US/docs/MDN/Community/Issues","doc":{"body":[{"type":"prose","value":{"id":null,"title":null,"isH3":false,"content":"<p>As a contributor, you can <a href=\"#guidelines_for_reporting_an_issue\">report</a> and <a href=\"#guidelines_for_working_on_an_issue\">work</a> on issues.\nAfter you report an issue, the issue gets triaged. Issue <a href=\"#guidelines_for_triaging_issues\">triaging</a> is typically done by people assigned the role of a maintainer or an owner.</p>"}},{"type":"prose","value":{"id":"general_guidelines_for_participation","title":"General guidelines for participation","isH3":false,"content":"<p>While reporting an issue or participating in a conversation in an issue, always ensure that your inputs are contributing to the overall progress of the project. Consider whether the issues you open and your comments in an issue are constructive and on topic and are not just adding noise.</p>\n<p>Do the following:</p>\n<ul>\n<li>Before filing an issue, consider if you need to <a href=\"/en-US/docs/MDN/Community/Communication_channels#chat_rooms\">discuss</a> it with the staff/community. Use discussions to gain different viewpoints and to converge on an agreed-upon course of action. This helps to keep issues focused and productive.</li>\n<li>After filing an issue, try to fix the problem yourself. Read our <a href=\"https://github.com/mdn/content/blob/main/CONTRIBUTING.md\" class=\"external\" target=\"_blank\">contribution guide</a> to learn more.</li>\n<li>If you have a question, you can ask it in the <a href=\"/en-US/docs/MDN/Community/Communication_channels#chat_rooms\">MDN Web Docs chat rooms</a> instead of filing an issue.</li>\n</ul>\n<p>Avoid doing the following:</p>\n<ul>\n<li>Complicating issues by trying to discuss multiple topics or by making off-topic comments.</li>\n<li>Opening lots of issues asking vague questions.</li>\n<li>Asking questions without trying to solve the problem yourself first.</li>\n</ul>"}},{"type":"prose","value":{"id":"guidelines_for_reporting_an_issue","title":"Guidelines for reporting an issue","isH3":false,"content":"<p><a href=\"https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues\" class=\"external\" target=\"_blank\">Issues</a> are used to track bugs. An issue must be a single actionable task or a collection of related actionable tasks and must have a clear outcome.</p>"}},{"type":"prose","value":{"id":"before_filing_an_issue","title":"Before filing an issue","isH3":true,"content":"<p>If you think you've found a bug with the content on MDN Web Docs or with the look and feel of the website, search the current open issues in the <a href=\"/en-US/docs/MDN/Community/Our_repositories\">relevant repository</a> and make sure nobody else has reported the issue.</p>"}},{"type":"prose","value":{"id":"reporting_an_issue","title":"Reporting an issue","isH3":true,"content":"<ul>\n<li>\n<p>Depending on the type of problem you've discovered, report it by filing an issue on one of the followings:</p>\n<ul>\n<li><a href=\"https://github.com/mdn/content/issues/new/choose\" class=\"external\" target=\"_blank\">documentation</a></li>\n<li><a href=\"https://github.com/mdn/translated-content/issues/new/choose\" class=\"external\" target=\"_blank\">translation</a></li>\n<li>the website's <a href=\"https://github.com/mdn/yari/issues/new/choose\" class=\"external\" target=\"_blank\">look and feel</a></li>\n<li>the \"Try it\" <a href=\"https://github.com/mdn/interactive-examples/issues/new/choose\" class=\"external\" target=\"_blank\">interactive example</a> section</li>\n<li><a href=\"https://github.com/mdn/dom-examples/issues\" class=\"external\" target=\"_blank\">DOM examples</a></li>\n<li><a href=\"https://github.com/mdn/learning-area/issues\" class=\"external\" target=\"_blank\">Learning area</a></li>\n<li>the <a href=\"https://github.com/mdn/browser-compat-data/issues/new/choose\" class=\"external\" target=\"_blank\">browser compatibility</a> information</li>\n</ul>\n</li>\n<li>\n<p>Choose the appropriate category to report the issue. For example, to report a content bug, use the <a href=\"https://github.com/mdn/content/issues/new?assignees=&labels=needs+triage&template=content-bug.yml\" class=\"external\" target=\"_blank\">Content issue</a> template in the <code>mdn/content</code> repository.</p>\n</li>\n<li>\n<p>Provide sufficient information while reporting the issue:</p>\n<ul>\n<li>\n<p><strong>Issue title</strong> must convey succinctly the <em>required action</em>.</p>\n</li>\n<li>\n<p><strong>Issue description</strong> must clearly describe the bug and the action required to resolve the issue. It must also list the task or sub-tasks to be completed to resolve the issue. Some other guidelines include:</p>\n<ul>\n<li>Use the description field to indicate the status of the task or sub-tasks by using checklists.</li>\n<li>Update the status of a task in the issue description instead of commenting on the issue. Use <a href=\"https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists\" class=\"external\" target=\"_blank\">task lists</a> in the description if an issue has multiple parts. This helps others who may otherwise need to scroll through comments on the issue to determine the status of various tasks.</li>\n<li>Comments in an issue should be limited to details or context that help resolve the issue.</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>\n<p>If the information you provide in the issue is incomplete, then you might be contacted later during the <a href=\"#review_the_issue_for_completeness_of_information\">issue triaging process</a>.</p>\n</li>\n<li>\n<p>If you find yourself in one of the following situations, move the conversation to <a href=\"https://github.com/orgs/mdn/discussions\" class=\"external\" target=\"_blank\">MDN's discussion on GitHub</a>:</p>\n<ul>\n<li>A discussion needs to take place to clarify an issue.</li>\n<li>A discussion begins after opening the issue.</li>\n<li>The issue has no clear consensus on its resolution.</li>\n<li>The requirements for completing the task expand while it's being resolved or the work is unclear.</li>\n</ul>\n</li>\n<li>\n<p>For minor and small bugs, you can <a href=\"#fixing_issues_yourself\">make the changes yourself</a> and submit a pull request.</p>\n</li>\n</ul>"}},{"type":"prose","value":{"id":"creating_a_task_list_issue","title":"Creating a task list issue","isH3":true,"content":"<p>If the issue you're opening is not to report a bug but to perform a series of tasks, you can create the issue as a <a href=\"https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists\" class=\"external\" target=\"_blank\">task list</a>.\nExplain the context or reason for performing the tasks in the description.\nEnsure that you list all the actionable tasks as a checklist.</p>\n<p>For example:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">markdown</span></div><pre class=\"brush: markdown notranslate\"><code>// Issue title\nEnsure sections follow the order defined in the CSS property template\n\n### Description\n\nThe CSS property page template is defined [here](/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types/CSS_property_page_template).\nThe task list in this issue will be used to compare the documented CSS properties with the template and track changes to the property pages for compliance.\n\n### List of pages checked\n\n- [x] [accent-color](/en-US/docs/Web/CSS/accent-color) - checked, okay\n- [ ] [backdrop-filter](/en-US/docs/Web/CSS/backdrop-filter)\n- [ ] [letter-spacing](/en-US/docs/Web/CSS/letter-spacing) - open pull request to move `Accessibility concerns` and `Internationalization concerns` sections before the `Specifications` section.\n</code></pre></div>"}},{"type":"prose","value":{"id":"guidelines_for_working_on_an_issue","title":"Guidelines for working on an issue","isH3":false,"content":"<p>Remember that if you take on an issue, the expectation is for the work to be completed in a timely manner. If you're not able to make any progress for a week after being assigned or can no longer complete the required task, leave a comment and unassign yourself from the issue.</p>\n<p>These are the general steps for working on an issue:</p>\n<ol>\n<li>\n<p><strong>Find an issue:</strong> If you're looking to contribute, search for issues with <a href=\"#set_other_labels\"><code>good first issue</code>, <code>help wanted</code></a> or <a href=\"#set_a_priority_label\"><code>p3</code></a> label. Most repositories have issues with these labels. You are welcome to browse and pick an issue that is suitable for your skill set. Another useful place to look for issues to work on is the <a href=\"https://github.com/orgs/mdn/projects/25\" class=\"external\" target=\"_blank\">MDN Contributors Task Board</a>. This project view lists open issues from multiple repositories. You can filter the list based on the topics (<code>Labels</code> column) you're interested in. See the description of some of the <a href=\"#set_other_labels\">labels</a> that get applied during the issue triage process.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nAn issue with the <code>needs triage</code> label indicates that the MDN Web Docs core team has not reviewed the issue yet, and you shouldn't begin work on it.</p>\n</div>\n</li>\n<li>\n<p><strong>Assign the issue to yourself:</strong> After finding an issue you'd like to work on, make sure that the issue is not assigned to anybody else. Add a comment saying you would like to work on the issue, and if you are able to, <a href=\"https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users#assigning-an-individual-issue-or-pull-request\" class=\"external\" target=\"_blank\">assign the issue to yourself</a>.</p>\n</li>\n<li>\n<p><strong>Do the research:</strong> Most issues need some investigation before work can start.</p>\n<ul>\n<li>Scope out the work that needs to be done. If you need to ask questions, ask them in the <a href=\"/en-US/docs/MDN/Community/Communication_channels#chat_rooms\">MDN Web Docs chat rooms</a>.</li>\n<li>If the issue is well-described, and the work is pretty obvious, go ahead and do it.</li>\n<li>If the issue is not well-described, and/or you are not sure what is needed, feel free to @mention the poster and ask for more information.</li>\n</ul>\n</li>\n<li>\n<p><strong>Make the changes:</strong> Fork and branch the repository. Do your work and open a <a href=\"/en-US/docs/MDN/Community/Pull_requests\">pull request</a> in the repository. <a href=\"https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue\" class=\"external\" target=\"_blank\">Reference the issue</a> in the pull request description. Depending on the files you've updated in the pull request, a reviewer will be assigned to your pull request automatically. (Teams per topic area are defined in the <a href=\"https://github.com/mdn/content/blob/main/.github/CODEOWNERS\" class=\"external\" target=\"_blank\">CODEOWNERS</a> file).</p>\n<p>After opening the pull request, if you find you no longer have the time to make changes or incorporate review feedback, let the team know as soon as possible in a comment in the pull request. This will help the team assign another interested contributor to complete the work on the pull request and close the linked issue.</p>\n</li>\n<li>\n<p>After your pull request has been reviewed and merged, you can mark the linked issue as closed. If you opened the pull request with <code>Fixes #<issue></code> verbiage, the issue will be closed automatically when the pull request is merged.</p>\n</li>\n</ol>"}},{"type":"prose","value":{"id":"fixing_issues_yourself","title":"Fixing issues yourself","isH3":true,"content":"<p>If you spot a bug — whether it's a problem with the website's look and feel or an error in documentation — you can try to fix it yourself. Learn how you can contribute by going through our <a href=\"https://github.com/mdn/content/blob/main/CONTRIBUTING.md\" class=\"external\" target=\"_blank\">contribution guide</a>.</p>\n<p>If the bug is small, such as a typo or a minor sentence improvement, or involves an uncontroversial fix, submit a pull request with the changes.</p>\n<p>For all other type of bugs, begin by <a href=\"#guidelines_for_reporting_an_issue\">opening the issue</a>. Add a comment about your intent to work on the issue and if possible, describe your proposed solution or steps to fix the issue.\nWait for the issue to be triaged, so that the MDN Web Docs team can verify that the issue is legit and approves your proposed solution.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nIf you open a pull request before the issue has been triaged, your time and effort might go waste if the linked issue is deemed invalid or the solution does not match the one expected by the MDN Web Docs team.\nAfter the issue is triaged, assign the issue to yourself.</p>\n</div>\n<p>Using the <a href=\"#guidelines_for_working_on_an_issue\">guidelines on working on an issue</a>, try to fix the problem by updating the appropriate source, such as:</p>\n<ul>\n<li>The MDN Web Docs content (in English) in the <a href=\"https://github.com/mdn/content\" class=\"external\" target=\"_blank\">content</a> repository</li>\n<li>The MDN Web Docs translated content in the <a href=\"https://github.com/mdn/translated-content\" class=\"external\" target=\"_blank\">translated-content</a> repository</li>\n<li>The MDN Web Docs website look and feel in the <a href=\"https://github.com/mdn/yari\" class=\"external\" target=\"_blank\">yari</a> repository</li>\n</ul>\n<p>Each repository includes useful information to guide you on how to contribute.</p>"}},{"type":"prose","value":{"id":"guidelines_for_triaging_issues","title":"Guidelines for triaging issues","isH3":false,"content":"<p>If you are a maintainer or an owner in the MDN Web Docs GitHub organization, you are responsible for triaging issues in one or more MDN Web Docs repository.</p>\n<p>The overall process for triaging includes some <a href=\"#general_triaging_tasks\">general</a> and some <a href=\"#issue-specific_triaging_tasks\">issue-specific tasks</a>.</p>"}},{"type":"prose","value":{"id":"general_triaging_tasks","title":"General triaging tasks","isH3":true,"content":"<ul>\n<li>\n<p>When an issue is opened, the <code>needs triage</code> label is set on the issue automatically. You can search for this label to look for issues that <a href=\"#issue-specific_triaging_tasks\">need to be triaged</a>. Contributors or anybody else should not work on the issue until the issue has been triaged. (Triagers should remember to remove the <code>needs triage</code> label after triaging the issue.)</p>\n</li>\n<li>\n<p>In the <a href=\"https://github.com/mdn/content/issues\" class=\"external\" target=\"_blank\">mdn/content repository</a>, an additional <code>Content:</code> label, such as <code>Content:CSS</code> or <code>Content:WebAPI</code>, is set on the issue automatically. This gets set based on the MDN URL mentioned in the issue. You can use the content-specific label to look for issues to be triaged in your specific topic area.</p>\n</li>\n<li>\n<p>If an issue concerns an active, non-en-US locale, set the appropriate label, such as <code>l10n-fr</code>, <code>l10n-zh</code>, or <code>l10n-ja</code>. The teams for those locales will pick these issues up and triage them.</p>\n</li>\n<li>\n<p>You don't need to actively triage issues all the time. Set aside time, say 30 minutes every week, to triage issues on a regular basis in your area of responsibility. Triaging doesn't have to be done as part of a synchronous meeting or even at the same time as everyone else, but it should be done regularly to make sure that the backlog of untriaged bugs doesn't get too high.</p>\n</li>\n<li>\n<p>Apart from triaging incoming issues every week, review the list of old bugs to see if there are any that are stalled, need closing, or are no longer relevant. The <code>idle</code> label is automatically set on issues that have had no activity for 30 days.</p>\n<ul>\n<li>Check assigned issues that are still open to see if the assignee is making progress. If there is no progress after a week of being assigned, ask them if they still have time to work on the issue. If another week passes by without any progress, unassign them and leave a comment indicating that you're making the issue available for other interested contributors.</li>\n<li>If a pull request has been opened to fix the issue but has not been reviewed for a week, give the reviewer a gentle ping to ask if they can get to it.</li>\n<li>If a pull request to fix the issue is waiting on review comments to be addressed after a week, then ask the author if they can respond to their review. If another week goes by, either fix the review comments yourself if you have time, or close the pull request and unassign the related issue.</li>\n</ul>\n</li>\n</ul>"}},{"type":"prose","value":{"id":"issue-specific_triaging_tasks","title":"Issue-specific triaging tasks","isH3":true,"content":"<p>These are the guidelines to follow while triaging each issue.</p>\n<h4 id=\"review_if_the_issue_is_valid\">Review if the issue is valid</h4>\n<p>These are some of the things to keep in mind while reviewing the validity of an issue:</p>\n<ul>\n<li>Check if the issue raised is valid and if the fix will improve the content for the readers and the website.</li>\n<li>Evaluate if the impact of the fix will be small or site-wide.</li>\n<li>Evaluate if the fix for the issue will need a discussion first, in which case, point the author to open a <a href=\"https://github.com/orgs/mdn/discussions\" class=\"external\" target=\"_blank\">discussion</a> instead.</li>\n<li>Check if the issue complies with our <a href=\"/en-US/docs/MDN/Writing_guidelines/Writing_style_guide\">writing guidelines</a> and <a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types\">templates</a>.</li>\n<li>Check whether suggestions for adding links comply with our <a href=\"/en-US/docs/MDN/Writing_guidelines/Writing_style_guide#external_links\">external links policy</a>.</li>\n</ul>\n<h4 id=\"review_the_issue_for_completeness_of_information\">Review the issue for completeness of information</h4>\n<p>Review each issue against the following checklist to ensure that the issue contains the described information for someone to start working on the bug:</p>\n<ul>\n<li>URL of the MDN Web Docs page with the problem or URL of an example MDN Web Docs page if the problem exists on multiple pages</li>\n<li>The specific heading or section on the MDN Web Docs page where the problem was found</li>\n<li>A clear description of the incorrect, unhelpful, incomplete, or missing information</li>\n</ul>\n<p>If any of the above information is not present, then you should ask the author of the issue to provide these details, and add the <code>needs info</code> label to the issue. Resume triaging the issue only after those details have been provided (after which, you can remove the <code>needs info</code> label). It is okay to wait for up to a week to get a response from the author.</p>\n<h4 id=\"set_a_priority_label\">Set a priority label</h4>\n<p>For each bug, set a priority label based on the severity of the issue to help people who want to work on the most important issues or areas.</p>\n<ul>\n<li>\n<p>Critical issue: This type of issue needs to be fixed as soon as possible, regardless of where it appears on the site. This type of issue could damage MDN's reputation severely and/or harm users. Examples of this issue include an incorrect code snippet, which if used in production, could create a severe security problem and undesirable content such as malware, profanity, pornography, hate speech, or links to such content.</p>\n<ul>\n<li>Label: <code>p0</code> (will be addressed immediately)</li>\n</ul>\n</li>\n<li>\n<p>Major issue: This type of issue could severely affect a page's usefulness. For example, a significant amount of out-of-date information, a complex and important code example that doesn't work, a significant amount of prose that is badly written and hard to understand, or a large number of broken links.</p>\n<ul>\n<li>Labels: <code>p1</code> (will be addressed soon) and <code>p2</code> (will be addressed soon, but higher priority items will take precedence)</li>\n</ul>\n</li>\n<li>\n<p>Minor issue: This is a type of improvement issue that can make the existing content better but does not affect learning or only has a minor effect on learning. Since these types of issues are not actively planned for, help from contributors to fix these issues is welcome and much appreciated. Fixing some of these issues can also provide the necessary practice to beginner contributors who are starting to get familiar with the contribution process. Examples include typos, bad grammar, a broken link, a small amount of out-of-date information or badly-written prose, or a code snippet that doesn't work.</p>\n<ul>\n<li>Labels: <code>p3</code> (no visibility when the issue will be addressed)</li>\n</ul>\n</li>\n</ul>\n<p>In general, critical issues should be fixed immediately and are most likely handled by MDN Web Docs staff and peers.</p>\n<h4 id=\"add_helpful_information\">Add helpful information</h4>\n<p>If possible, add information that can help contributors to fix the issue. The information can be in the form of steps, general approach, links to other similar fixed issues, or reading resources. A well-laid out plan or steps is especially required in issues that are labeled <code>good first issue</code> and can help ramp up new contributors quickly. You can time-box this task to 5-10 minutes.</p>\n<p>For example, as a triager, you can add the following information to the issue you are triaging:</p>\n<div class=\"code-example\"><div class=\"example-header\"><span class=\"language-name\">md</span></div><pre class=\"brush: md notranslate\"><code>To whoever fixes this issue, it looks like the following is needed:\n\n- Update the first paragraph below heading X to correct the problem with Y\n- Add a description of X\n- Update the compatibility data at Link-X\n</code></pre></div>\n<h4 id=\"set_other_labels\">Set other labels</h4>\n<p>Next, set the following labels as appropriate:</p>\n<ul>\n<li>\n<p><code>effort: small</code>, <code>effort: medium</code>, <code>effort: large</code>: Some contributors like to search for bugs based on the time and effort that will be needed to fix the bug. So where possible, you should try to provide an estimate of the required effort.</p>\n</li>\n<li>\n<p><code>good first issue</code>: Set this label on the issue if the fix for the issue is really simple and if fixing the issue would provide good practice for a newcomer who is getting used to the process.</p>\n</li>\n<li>\n<p><code>help wanted</code>: Set this label if the issue requires help from someone who knows about or is familiar with the topic. This is a popular label and some contributors use it to search for issues to work on in open source projects in their areas of familiarity or expertise.</p>\n</li>\n<li>\n<p><code>broken link external</code>: Set this label if the issue involves a broken link to an external page.</p>\n</li>\n<li>\n<p><code>document not written</code>: Set this label if the issue involves a necessary document that has not been written yet, usually because a link points to it.</p>\n</li>\n<li>\n<p><code>needs content update</code>: Set this label if the issue fix in another repository will need an equivalent fix in the <code>mdn/content</code> repository.</p>\n<div class=\"notecard note\">\n<p><strong>Note:</strong>\nAfter the triage process is complete, remove the <code>needs triage</code> label.</p>\n</div>\n</li>\n</ul>"}}],"isActive":true,"isMarkdown":true,"isTranslated":false,"locale":"en-US","mdn_url":"/en-US/docs/MDN/Community/Issues","modified":"2025-01-31T16:22:51.000Z","native":"English (US)","noIndexing":false,"other_translations":[{"locale":"de","title":"Erstellen und Bearbeiten von Issues","native":"Deutsch"},{"locale":"fr","title":"Bonnes pratiques GitHub pour MDN","native":"Français"},{"locale":"ja","title":"課題の作成と作業のガイドライン","native":"日本語"},{"locale":"ru","title":"Как сообщить о проблеме в MDN","native":"Русский"},{"locale":"zh-CN","title":"创建和解决议题指南","native":"中文 (简体)"}],"pageTitle":"Creating and working on issues - MDN Web Docs | MDN","parents":[{"uri":"/en-US/docs/MDN","title":"MDN Web Docs"},{"uri":"/en-US/docs/MDN/Community","title":"Resources"},{"uri":"/en-US/docs/MDN/Community/Issues","title":"Creating and working on issues"}],"popularity":null,"short_title":"Creating and working on issues","sidebarHTML":"<ol><li class=\"section\"><a href=\"/en-US/docs/MDN\">MDN Web Docs</a></li><li><a href=\"/en-US/docs/MDN/Tutorials\">Tutorials</a></li><li><a href=\"/en-US/docs/MDN/Guides\">Guides</a></li><li class=\"toggle\"><details open=\"\"><summary>Community resources</summary><ol><li><a href=\"/en-US/docs/MDN/Community\">Resources</a></li><li><a href=\"/en-US/docs/MDN/Community/Getting_started\">Getting started</a></li><li><a href=\"/en-US/docs/MDN/Community/Our_repositories\">GitHub repositories</a></li><li><a href=\"/en-US/docs/MDN/Community/Open_source_etiquette\">Open source etiquette</a></li><li><em><a href=\"/en-US/docs/MDN/Community/Issues\" aria-current=\"page\">Creating and working on issues</a></em></li><li><a href=\"/en-US/docs/MDN/Community/Pull_requests\">Pull request submission and reviews</a></li><li><a href=\"/en-US/docs/MDN/Community/Discussions\">GitHub Discussions</a></li><li><a href=\"/en-US/docs/MDN/Community/Translated_content\">Localization</a></li><li><a href=\"/en-US/docs/MDN/Community/Roles_teams\">Roles and teams</a></li><li><a href=\"/en-US/docs/MDN/Community/Communication_channels\">Communication channels</a></li><li><a href=\"/en-US/docs/MDN/Community/Learn_forum\">Learn forum</a></li></ol></details></li><li class=\"toggle\"><details><summary>Writing guidelines</summary><ol><li><a href=\"/en-US/docs/MDN/Writing_guidelines\">Writing guidelines</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/What_we_write\">What we write</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Writing_style_guide\">Style guide</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Learning_content\">Learning content guidelines</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Experimental_deprecated_obsolete\">Experimental, deprecated, and obsolete</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Attrib_copyright_license\">Attribution and copyright licensing</a></li><li class=\"toggle\"><details><summary>How-to guides</summary><ol><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto\">Overview</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Write_a_new_entry_in_the_glossary\">Add a glossary entry</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Images_media\">Add media</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Creating_moving_deleting\">Create, edit, move, or delete pages</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Document_a_CSS_property\">Document a CSS property</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Document_an_HTTP_header\">Document an HTTP header</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Document_web_errors\">Document errors</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Research_technology\">Research a technology</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/JSON_Structured_data\">Use structured data</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Write_an_api_reference\">Write an API reference</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Howto/Markdown_in_MDN\">Write in Markdown</a></li></ol></details></li><li class=\"toggle\"><details><summary>Page structures</summary><ol><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures\">Overview</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Banners_and_notices\">Banners and notices</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Code_examples\">Code examples</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Compatibility_tables\">Compatibility tables and the browser compatibility data repository (BCD)</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Feature_status\">Feature status</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Links\">Link macros</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Live_samples\">Live examples</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types\">Page types</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Sidebars\">Sidebars</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Specification_tables\">Specification tables</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Syntax_sections\">Syntax sections</a></li><li><a href=\"/en-US/docs/MDN/Writing_guidelines/Page_structures/Macros\">Using macros</a></li></ol></details></li></ol></details></li></ol>","sidebarMacro":"mdnsidebar","source":{"folder":"en-us/mdn/community/issues","github_url":"https://github.com/mdn/content/blob/main/files/en-us/mdn/community/issues/index.md","last_commit_url":"https://github.com/mdn/content/commit/719645a32546d9e514ac530a5eb66aa4c26d4f51","filename":"index.md"},"summary":"As a contributor, you can report and work on issues.\nAfter you report an issue, the issue gets triaged. Issue triaging is typically done by people assigned the role of a maintainer or an owner.","title":"Creating and working on issues","toc":[{"text":"General guidelines for participation","id":"general_guidelines_for_participation"},{"text":"Guidelines for reporting an issue","id":"guidelines_for_reporting_an_issue"},{"text":"Guidelines for working on an issue","id":"guidelines_for_working_on_an_issue"},{"text":"Guidelines for triaging issues","id":"guidelines_for_triaging_issues"}],"pageType":"mdn-community-guide"}}</script></body></html>