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
Next: Root
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
Depending on your team or organization's needs, you may want to make certain fields required to ensure that you're gathering the right information at the right time. Note that all required fields must be added to the Create Issue screen for associated projects and issue types, and that hidden fields cannot be marked as required.
Select > Issues.
In the Fields section, click Field configurations.
Click Configure next to the field configuration you wish to edit.
You will see “Required” next to fields that have already been marked required. Click Optional to remove this requirement.
To make an optional, visible field required, simply find the field and click Required.
Hi @hcheng
You tag the question as JIRA Server related but shoot out Cloud documentation. Always make sure to read documentation for the product you are using.
Regarding your auestion, reauired field are defined in a Field Configuration, then you can associate this field configuration to a Field Configuration Scheme that will associate Field Configuration to an issue type. At this time you have not set require any field for any project, you need to associate the configuration scheme to a project. So, field optional or reauired can be set by project you just have to create a new field configuration and field configuration scheme.
You are talking about Tenplate project, so if it's on server it's most likely that you create a project using shared configuration base on an existing project you called Template, in this case if you change the configuration of the new project it will impact all project the configuration is shared with, so you have to create new field configuration and field configuration scheme to avoid that.
You can see on top of each field configuration if it's use by N project.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.