You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have been trying to set the Due date on our Epic issue mandatory when creating issues.
Is it possible to not allow people to create issues without putting in the Due date( and start date- custom filed) and also want to customize it for different issue types and possibly different projects?
We want to use this for our annual workload report that we are creating and instead of asking people to not forget to input the due date we wanted to make it mandatory so that we will not miss any data.
If I am understanding you correctly, yes, you can create a separate Field Configuration per Issue type for the project's Field Configuration Scheme and each Field Configuration can make different fields mandatory.
So, you can create a Field Configuration for Epics and set the Due Date ad Required. But have a different Field Configuration for other issue types where the field is not required.
See this article for more guidance: https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-field-configurations/