Difference between context and field configuration in setup

[Gergely Fehér]

As I tried it seems I can eliminate a field from an issues screens in a project by creating an issue filed context - leaving out the specific issuetype/project, or assign a field configuration to it where it is hidden. Is there any differences between the 2 concepts? Are there any "best practices" when to use the context, and when do I need field configurations?

[Joe Pitt · Accepted solution]

They serve totally different functions.

Context allow you to have different values in select lists for different issue types or projects. 

Field configurations let you set fields required at creation or hidden fields in a project by issue type. 

Required fields, at creation time are controlled by the field configuration scheme. That scheme is composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme.  Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html