Related to #45084

As I and many others have already written: we want this functionality!
https://github.com/orgs/community/discussions/51500

For the Apache Fondation it was finally also allowed!

@azenMatt - this is something I check consistently. I and many others have laid out reasons here: https://github.com/orgs/community/discussions/4264#discussioncomment-6071942.

I continually wonder why the decision to enforce the required fields wasn't carried over, yet it's still something we can add to a form is. Is there any possibility this will be coming soon at all?

does not complete the form due to laziness

These forms should help with exactly this —otherwise, they might as well be markdown templates. There's literally no point in them at the moment in our repos. It's just a completely wasted feature. I cannot describe how much benefit this would have to our internal support teams triaging bug reports written by first and second line.

I've been trying to work around the lack of a preview feature by testing my issue template changes in a private repo before inflicting them on real users. (Call me old fashioned but I don't think it's a good idea to put un-tested YAML changes into production.) It's really unfortunate that the exact same issue template does different things in different repos.

This severely degrades the utility of issue forms in an org. The ability to require a field would have significantly eased the work required to chase people around asking for more information.

While it is true that the same users creating an issue can edit the issue as markdown without the form, a carefully considered set of required fields and a restriction to prevent initial creation using plain markdown would make a daily difference.

The level of disinterest towards its (business) customers and the inaccessibility of rational arguments is quite impressive/pity.
That people are not given the freedom to decide for themselves how they act internally, just to enforce their own agenda/world view...

My labels work fine though, without any issues. Mores when the labels that have emoji in them.

I found that labels only work if the label already exists in the repo. If it doesn't exist it will not be added.

I found out today that not only does the label need to be in the repo that you are creating the issue in, it needs to be in the orgs .github repo as well... Took forever to figure that out. You also have to give anyone you want to add as a template assignee write access to the .github repo....