Hey Reynalda,
The scheme is attached to the project and can be made up of multiple Field Configurations. Each Field Configuration can be attached to one or more Issue Types. The result is that you can make certain fields Required for certain issue types on a project but not others.
John: I'm not understanding the statement you made. Can you direct me to sites or links that explain this in more details. Thank you for answering my questions but I'm still not understanding this. Sorry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure - here is the link to the Field Configuration guidance.
https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
John: I THANK YOU and understood the field required and hidden but I need to understand the Field Config. and and the Field Config Scheme?
Sorry, just trying to learn more about this topic.
THANK YOU so much for the help!!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Reynalda - I am happy to help. :-)
Did the document help you to understand better? Do you still need additional help?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need to understand what is
Sorry, I'm not trying to be difficult just trying to learn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries.
The Field Configuration tells the system what fields should be required when the issues are created. It also can be used to help text for the field.
But the Field Configuration is actually created for one or more issue types. So if you want the Description field, for example, to be required for all issue types for that project, then you just have one Field Configuration.
But if you want Description to only be required, for example, for Tasks, then you would create one Field Configuration for Tasks where the Description is required, and one Field Configuration for all other issue types.
Both field configurations would be place under a single Field Configuration Scheme because it is the Scheme that actually gets attached to a project.
Does that help?
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.