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

Screen overview - Jira Tutorial

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

Start my 1-month free trial Buy for my team

Screen overview

“

- In this overview, we'll discuss the different types of screens, and how they're used to collect information from users. Screens define which fields are present and their display order. On the left is a screen a user sees when creating an issue. On the right is the admin's view of the same screen and the fields displayed on it. Screens have a name, an optional description, a list of associated fields that appear on them, and optional tabs used to group related fields, and here's a tip. A field can be present on a screen, but it can be invisible to the end user if hidden in a Projects field configuration scheme, and in Cloud, it can also be hidden when emptied by layout settings. Jira lets you define the order of some fields, but not all. For example, the summary field is hard coded to display at the top of the page regardless of where you order it on a screen. Multi-line fields appear in the main content section in the left or in a tab. In Cloud, fields with values are shown in a collapsible Details panel, and fields without values appear in a panel labeled More Fields. Atlassian says that the first place users look when they open a work item is in the area on the left, so you should put your most important fields there. If your layout screen is configured with more than one tab, the other tabs will appear in this section. Only tier admins can configure tabs. Project admins can't change the order of the fields displayed on the tab. If your screen includes tabs, they'll display in this area. Only tier application admins can create tabs and determine the order. The section at the top right, labeled Details, generally contains context fields. These fields display secondary information that is used to sort, filter, or search for information. In Cloud, end users can customize this area by pinning the context fields they use most often to the top of the list. The right sidebar also contains additional context fields and panels. Sometimes you'll see additional features in this area provided by integrations or third-party apps. Jira has different types of screens for different uses. In Cloud, there are screens for creating, viewing, and transitioning issues in a workflow. In server and data center, there's an additional screen for editing. Here's an example of each. A Create screen is what the user sees when they create an issue, and a View screen is what they see when they view an issue. The ability to have two separate screens for these different user actions allows the administrator to place a subset of fields on the Create screen. Think about the user experience of creating a Jira issue. You want the experience to be as quick and easy as possible. I recommend only asking for the minimal amount of information, and only for data that the creator can provide. For example, does the person creating an issue select a due date at the time of creation? Usually an issue is created and needs to be reviewed for understanding, estimated, and prioritized before a due date can be determined. In this case, there's no value in putting the due date field on the Create screen. Collect that information later in the workflow on a transition screen instead. In Server and Data Center, there's an additional screen for editing issues. There's no edit screen in Cloud because issues are edited in line directly from the view screen. Finally, Jira also has transition screens that show when issues are moved from one status to another in a workflow. In the example, the transition screen shows the due date field and the time tracking field. The screen is shown to the user when the Start Progress transition is clicked in a workflow.

Contents