I’ve just checked and it isn’t clickable (just two plain <div>s – note for us (triagers) there’s no ‘settings cog’ similar to milestones/labels on the screen. We also can’t link issues and PRs (the “Development” heading).
Do you want to “Give Feedback” to GitHub using the link on the project page? Assuming you have that link.
I can do it if you don’t want to, but it’s probably better from a triager in case they need to follow up.
(FWIW, I’ve asked Discourse moderators to move the “GH Projects vs. triagers” tangent, so we can focus on unsupported platforms again.)
(Replying so that this comment gets dragged out along with the others in the thread split)
There’s some additional context on this core-worklow issue, and three threads on the same feedback repository that the ‘give feedback’ link points to. Hugo and I at least have voted in support of the linked feedback issues (primarily this thread) – I’m not sure if the best approach would be to open a new one, or comment on an existing one. None of them have any comments by a GitHub staff member, though.
There might be a way to give triagers, or at least trusted triagers, this feature and the others we’ve been asking for without giving them any ability to push, merge to or otherwise modify any branches on the repo, without waiting (potentially forever) for GitHub to add each of them—use branch protect to restrict creating, pushing and merging for all branches to only teams that currently have write access (so there’s no change for them), and then grant triagers (or a sub-team of trusted triagers) the “write” role, which allows them to use these various GitHub UI features without being able to actually modify anything on the repo itself. See my comments on the issue for more.