What are JIRA system fields, and what options are available in them?
- [Instructor] Let's start by going over system fields. Fields represent the different data points where you enter in or select values. These fields capture that relevant data. Anytime you open up a create, edit, or view screen, the fields you see on those screens are represented in your instance as system or custom fields. There are many different types of fields such as text entry, single select drop down, multi select, or radio. If you're familiar with using standard webpages, creation administration of fields within JIRA should be relatively easy.
We're going to start this lesson by selecting the Issues dropdown and under Recent Issues, select any of them. This will bring up that issues view screen. Under the detail section, you'll see many different types of fields such as type, priority, status, and resolution. Other fields such as affects version, fix version, components labels, and even description are also system fields. These fields will not have a lot in terms of additional configuration options available to you as they are required to work correctly in order for your instance to function.
It's for this reason that the options available to you for system fields are relatively limited compared to those same options for custom fields. Let's go ahead and hit the administration cog and then we'll select Issues. After the issues section opens, scroll down. Under Fields, select Custom Fields. Let's scroll down this list. As you'll see, there's quite a few fields that may not seem familiar to you at first glance. Take Epic Color and Epic Link, for example. These carry the stamp locked in next to the name.
This denotes a system field that has limited options compared to some of the other fields in this list. You'll also notice things like Parent Link, Rank, and Sprint are locked. When you scroll through here, you'll see other fields that don't necessarily have the locked stamp but that doesn't mean you didn't create them. JIRA will spin up a variety of fields when the instance is created. On the left hand side, you'll see Issue Attributes with status, resolutions, and priorities listed underneath. These are also system fields that are controlled on the system level but aren't located on the custom fields section.
First click Statuses. Now, on this status list, you'll see every single status currently located in the instance. You'll notice statuses that you entered on your workflow creation now exist on this list. This is important. You can add new values to this system field but you can't edit it at its core. Statuses are integral to the functionality of JIRA and through this screen you can add more of them but you can't change the properties of the field itself. For example, you can't change the field to read something other than status as its name, it will always be called status.
Any new status that you add and any new workflow will be added as a value within this list. You can also add a status here by clicking Add status and you can provide the same information you would on a workflow design screen. You also have the ability to translate the status value using the translate status button if you have localization requirements. We will not be going into localization configuration in detail in this video. Back down to the Issue Attributes menu, go ahead and click Resolutions. This functions the same as Statuses.
You can view all the resolutions but you cannot change the field itself, it will always be known as Resolutions. To add a resolution, add your value here. After typing in your new resolution name, click the Add button. This is the only place you can add new resolution values. Later on, I'll show you how to limit selectable resolutions on workflow transitions. Underneath Resolution, click Priorities. This will display all the different priorities that are currently available within your system.
If these values aren't necessarily compatible, you can add new ones to the list and edit or replace the default values to anything you need. To add a new priority, simply enter the new value in the Name field, select an image icon, click in this box to select a color, select OK, and then click Add. You can delete any priority by simply clicking Delete and confirming the action. You can also make any of your priorities the default by simply clicking the Default link next to the priority.
System fields are necessary for your instance to function correctly. As a best practice, you should make sure you aren't adding new values if an existing value for any of these system fields can function as a reasonable substitute. For example, if you already have the highest as a value in your priorities and a project administrator requests a most urgent priority to be added, ask him if the highest priority is a reasonable substitute. More often than not, you'll find that you can come to a reasonable comprise without having to add new shared objects that can affect performance and stability of your instance over time.
- Configuring and editing a custom field
- Creating and editing field configuration schemes
- Copying a screen
- Creating a new screen scheme
- Adding fields
- Creating advanced workflows
- Issue security
- JIRA notifications
- Creating a new event
- Firing a custom event in a workflow