Severity

[sstrubberg]

Brief

As a maintainer of the Core Components of Carbon, I would argue that we have an incredibly polished process for triaging defects in our codebase and turning those bugs around into fixes in our regular sprint cadence.

However, I think things tend to fall apart when we extend the idea of triaging and fixing defects in the other pillars of our design system, our Figma kit and our Documentation. This PR aims to remedy that with a comprehensive point-of-view on our approach to applying severity to not only our Code, but our Kit and Docs as well.

Testing

To review, click on the Files changed tab above, then click the button to display rich diff.

Scroll down to the Triaging section to see the table.

I'm looking for feedback on not only these descriptions, but on the very idea of assigning severity to defects in not just our code, but our docs and our kits as well.

[netlify]

✅ Deploy Preview for v11-carbon-react ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	37a578b
🔍 Latest deploy log	https://app.netlify.com/sites/v11-carbon-react/deploys/668d7edbbccefc0008588b85
😎 Deploy Preview	https://deploy-preview-16921--v11-carbon-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for carbon-elements ready!

Name	Link
🔨 Latest commit	37a578b
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-elements/deploys/668d7edb1d9e710008afaa2e
😎 Deploy Preview	https://deploy-preview-16921--carbon-elements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[aagonzales]

Initial thought on docs, I think we could break down "missing" into major and minor pieces.

Docs Sev 2: "The documentation is wrong or missing major details".

Docs Sev 3: "The documentation is mis-leading, somewhat true, or missing minor details"

• Sev 3 does not impact the users understanding of how to use the component. Something like maybe a token was missed on the style tab.

[tay1orjones]

Looks good! One minor suggestion on the first column

[aagonzales]

I think these are good for general descriptions. I think at some point we could better define what is considered "major" versus "minor"

[sstrubberg]

I think these are good for general descriptions. I think at some point we could better define what is considered "major" versus "minor"

Agreed. In my mind, as we start to tackle these types of issues, we'll start to find harden our POV on major vs. minor. What's important is that we're identifing defects and having the conversations.

[alisonjoseph]

❤️

[elycheea]

I apologize for nitpicking. We have some inconsistent usage of workaround, work-around, and work around. 😉

[sstrubberg]

I apologize for nitpicking. We have some inconsistent usage of workaround, work-around, and work around. 😉

no apology needed! Fixing now!

[laurenmrice]

Thanks for doing this, Scott!

[oliviaflory]

Thank you Scott!