Hi @mgilliam,

Thanks for clearly describing the issue-this change in Markdown rendering on the milestones index can definitely disrupt workflows that rely on formatted milestone descriptions.

What’s Happening:
As you’ve observed, Markdown in milestone descriptions now only renders on the individual milestone page, not on the milestones overview/index, where it appears as plain text. This is likely due to a recent change or regression in how GitHub displays milestone data on the index page.

Current Workarounds:

1. Direct Linking:
   If you rely on users seeing formatted content, you can add a note in the milestone title or description with a direct link to the milestone’s detail page (where Markdown is rendered correctly).

2. Copy Plain Text:
   For now, you may need to copy essential information (like key dates) into the description in a plain text format for the index, alongside the Markdown table, to ensure visibility.

3. Feedback:
   Since this behavior worked previously, it could be an unintended regression. I recommend submitting this as a bug through GitHub’s feedback channels (which you’ve already done here). You can also use the "Give feedback" option at the bottom of the milestones index page to highlight that Markdown rendering is important for your use case.

Long-term:
There’s no user-side fix to force Markdown rendering on the index page, but by providing clear feedback (as you’ve done), you increase the chances of the GitHub team addressing this in a future update.

If Markdown rendering in milestone overviews is critical for your project management, you might consider using GitHub Projects or Discussions as a temporary alternative, as both support richer formatting.

Summary:

• No immediate fix to restore Markdown on the milestone index.
• Use milestone detail links and plain text as workarounds.
• Keep feedback channels active to help prioritize a fix.

Hope this helps clarify the situation and provides some practical next steps!