From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Identifying standard fields - Jira Tutorial

From the course: Complete Guide to Jira Administration: Configuration, Management, and Automation

Start my 1-month free trial Buy for my team

Identifying standard fields

“

- Jira comes with multiple built-in standard fields like summary, description, priority, comments, and others. The summary field is the one and only field that's required by Jira in all Jira issues. As an administrator, you can require additional fields on the Create screen and during a workflow transition, but summary is required by background logic that you and I cannot modify. Some standard fields have settings that you can modify. For example, you can add user instructions to the description field or change the input it accepts from Wiki markup to plain text. These kinds of changes are made in a field configuration, which we'll explore in an upcoming course section. Some standard fields, like priority, have their own entire configuration pages in the application admin area and other standard fields have no settings for you to modify at all. Some standard fields are built into all application types, and others are application specific. Here are some fields you'll see in all types of Jira. And here are some standard fields in Jira Software and Jira Service Management. If you created a new application for this course, right now is the perfect opportunity to make a list of standard fields that are already present. It's much harder to separate standard fields from custom fields later after the field list has grown. Make a list now or use the list of standard fields in different Jira application and deployment types on my website. In Server and Data Center, there's a page in the Issues admin area that lists system fields and the screens that use them.

Contents