Custom Fields No Longer Visible or Editable on Issues (Web Only) #183897
Replies: 4 comments 5 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
This definitely sounds frustrating—and the fact that it still works in the mobile app is a very useful clue. Based on what you’ve described, here are the most likely causes and some concrete things to check, ordered from “most likely / seen before” to “longer shot but worth ruling out”. Key insight from your symptoms
This strongly suggests the problem is not with the Project configuration, but with how the web UI is resolving Issue ↔ Project field metadata for that specific repository. The mobile app using a different rendering path is consistent with this being a GitHub web UI / feature-flag regression, not a permissions issue. Things that are unlikely to be the causeYou can mostly rule these out already:
Most likely causes1. Issue Types / Custom Fields backend outage or partial disableThe message:
is not a normal permission error. That message appears when:
This has happened before during silent rollouts or regressions. Why this fits perfectly
👉 This strongly points to a GitHub-side regression, not something you broke. 2. Repository-level feature flag corruptionGitHub rolls out Projects v2, Issue Types, and custom fields behind per-repo and per-org flags. Sometimes a repo ends up in a bad state where:
This explains why:
You cannot fix this yourself. 3. Private repo + Projects v2 edge caseThere have been prior bugs where:
…lose field rendering in the issue UI only. Again: GitHub-side. Things you can try (low effort, may unstick it)These are safe and reversible:
If new fields also don’t show, that further proves backend corruption. What to do next (recommended)✅ Open a GitHub Support ticket (this is the real fix)This is absolutely support-worthy. When you do, include:
Use language like:
That helps route it to the right internal team faster. TL;DR
|
Beta Was this translation helpful? Give feedback.
-
|
Fantastic! Thank you so much for the reply! I already have a support ticket opened (https://support.github.com/ticket/personal/0/3994150) - just waiting on a reply there. The low effort things I could try that were mentioned have both already been attempted with no improvement unfortunately. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @jwinn-lgtm, thanks for being a part of the GitHub Community! Are you still experiencing this issue? |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Feature Area
Issues
Body
Hi everyone — we’re running into a blocking issue with GitHub Projects and custom fields and would really appreciate any insight or guidance.
Summary
Myself and another engineer, working on separate machines and browsers, are suddenly unable to view or edit custom fields on GitHub Issues via the web UI for our project: OpenDigitalAsset (ODA). These fields (e.g. start date, sprint, type, etc.) were previously visible and working without issue.
Notably, the same issues do display and allow editing of custom fields in the GitHub mobile app, which makes the behavior even more confusing.
What’s happening:
Scope
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions