Thank you for watching, voting, and commenting on this issue. We use this data as well as many other inputs to feed into our prioritisation process.
Allowing teams to have required fields on issue creation is something that will be available in next-gen, although it is not something that we will be focusing on in the next 6 months. We want to share this with you to ensure you can plan out your use of projects within Jira Software effectively. In the short term we recommend teams use classic projects when you need to mark certain fields as mandatory on issue creation.
We understand this is highly requested and seems like it should be quite basic to deliver, however we have some groundwork to undertake around the issue create experience which is a dependency for this work. We are prioritising the performance and scalability of the issue create experience as a first, and we will then get to overhauling the user experience of the global issue create view. We apologise for the inconvenience this is causing you.
It is worth calling out that it is possible to use the "Check an issue's field" workflow rule to ensure a field is populated on transition of an issue (e.g. from "To Do" to "In Progress"). This may be sufficient for some of you, although it doesn't cater for the scenario where you need this data captured when the issue is first created.
Please do continue to vote and in particular please continue to add comments on how your teams find value with having required fields on issues. This contextual information of what you are doing and why you are doing is invaluable for us in providing you with a product that will grow with your needs.