Jira Admin Essentials (Part 4): Fields, Screens & Permissions (What Users See and Can Do)

Welcome back! This is Part 4, and the final episode of the Jira Admin Essentials mini tutorial series. In this video, we cover fields, screens, and permissions: what users see, what they can edit, and what they’re allowed to do. Marvin is a Technical Support Engineer (DevOps) at re:solution GmbH. He walks you through the core building blocks of Jira configuration and shows the “admin sanity rules” that help you avoid slow, confusing Jira setups. What you’ll learn in this video 1) Fields (the data you capture) Jira has standard fields like: • Summary, Description, Priority But admins can also create custom fields like: • dropdowns/select lists • date pickers • user pickers • status-like fields (custom) Important warning: too many fields can make Jira slow and confusing. Create fields only when you’ll actually use the data. 2) Field configurations (rules for fields) Field configurations control whether fields are: • required • hidden • given default behaviors This is how you simplify the create form: • hide rarely used fields • require only what’s essential 3) Screens (what users actually see) Screens control which fields appear on: • Create • Edit • View Key distinction: • Field configuration = rules • Screens = visibility 4) Permissions (the security side) Permission schemes define who can: • browse projects • create issues • edit issues • transition workflows • administer projects Permissions can be assigned via: • groups • project roles • specific users 5) Project roles + scalable permission management Project roles (e.g., Admin, Developer, Viewer) are assigned at the project level and referenced in permission schemes, making access control consistent and scalable. 6) Issue security (for sensitive work) If you need restricted visibility inside a project, use Issue Security levels (configured via an Issue Security Scheme). This may need to be enabled/set up per project. 7) Audit log (know who changed what) The Audit log helps you track admin changes: • who changed what • when it changed • what was affected This is critical for troubleshooting and governance. Your “next step” exercise (high value) Open one real project and identify these three: 1. Issue Type Scheme 2. Workflow Scheme 3. Permission Scheme That alone will teach you how Jira is “wired” in your instance. #Jira #JiraAdmin #JiraCloud #Atlassian #JiraPermissions #JiraConfiguration #ProjectRoles #IssueSecurity #AdminTips #ITAdmin