JIRA

Install

Admin

Use

	JIRA Administrator's Guide Introduction Getting Help Look and Feel Logo, Colours and Timezone Configuring the default Language Configuring the default Issue Navigator Configuring the default Dashboard Overview of Dashboard Portlets Enabling Portlets and Other Plugins Editing the Announcement Banner Enabling Logout Confirmation Email Email Overview Creating a Notification Scheme Customising Email Content Creating Issues & Comments from Email SMTP configuration User Management Managing Users Managing Groups Managing Project Roles Migrating from Groups to Project Roles Enabling public signup and CAPTCHA Integrating JIRA with LDAP Integrating JIRA with Crowd Configuring Trusted Applications Security Overview Global permissions Project permissions Issue security Project Management Defining a Project Assigning members to Project Roles Defining Project Components Defining Project Versions Creating Release Notes for a Version Configuring Project Keys Configuring Fields and Screens Overview Concepts Defining 'Resolution' field values Defining 'Priority' field values Defining 'Status' field values Defining 'Issue Type' field values Associating Issue Types with Projects Translating Resolution/Priority/Status/Type Configuring field behaviour Configuring rich-text renderers Associating behaviour with Issue Types Placing fields on screens Associating screens with Issue Operations Associating screens with Issue Types Creating & configuring Custom Fields Custom Field Overview Adding Custom Fields Configuring Custom Fields Configuring Workflow Workflow Activating Workflow Events Importing from Other Systems Importing from Bugzilla Importing from Mantis Importing from FogBugz Importing from Excel/CSV Moving or Archiving Individual Projects Overview Archiving a project Merging JIRA instances Splitting JIRA instances Integrating with Source Control Integrating with CVS and ViewCVS Integrating with Subversion Integrating with Perforce Integrating with ClearCase Integrating with FishEye Configuration Options & Settings Global Settings Enabling Issue Linking Enabling Sub-tasks Enabling Trackback linking Enabling Time Tracking Enabling File Attachments Enabling Thumbnails for Attachments Server Administration Indexing & Search Backing up Data Automated Backups Restoring Data Database Integrity Checker Increasing memory Performance Tips Database Indexing Precompile JSP pages Logging and Profiling Thread Dump Downgrading (Ent to Pro) Downgrading (Ent to Std) Downgrading (Pro to Std) Using robots.txt with Search Engines Appendix A - Extending JIRA Extension Overview Listeners Services Jelly tags JIRA Toolkit Customising Text Developer Guides JIRA Plugins JIRA RPC Overview Creating a SOAP Client Creating an XML-RPC Client Creating Custom Field Types Custom Workflow Elements Creating new Portlets Creating new Reports More.. JIRA Source Building JIRA from source API Documentation

Configuring Fields and Screens: Overview

PDF

To help you tailor JIRA to your organisation's needs, JIRA enables you to manipulate the display and behaviour of issue fields ('Summary', 'Description', 'Issue Type', etc).

You can:

Change a field's description
Make a field hidden or visible
Make a field required or optional
Add your own values for 'Issue Type', 'Priority', 'Resolution' and 'Status'
Create new 'custom' fields
Enable a rich text renderer for (some) fields
Position fields on a screen
Choose which screen should be displayed for each issue operation (e.g. 'Create Issue', 'Edit Issue') or workflow transition (e.g. 'Resolve Issue', 'Close Issue')

Concepts

Some key JIRA concepts include:

Field Configuration — a set of definitions for all fields, comprising: each field's description; whether each field is hidden or visible; whether each field is required or optional; and what type of renderer to use for each text field.
Screen — defines which fields are present on a screen, and their order. (Note that a hidden field can be present on a screen, but will still be invisible.)
Screen Scheme — associates different screens with different issue operations (e.g. 'Create Issue', 'Edit Issue', 'View Issue') and (in Professional Edition only) projects.
(Enterprise Edition only) Issue Type Screen Scheme — associates Screen Schemes with issue types and projects.
(Enterprise Edition only) Field Configuration Scheme — associates Field Configurations with issue types and projects.
(Professional and Enterprise Editions only) Issue Type Scheme — associates issue types with projects.

Below is an overview of the functionality available in the three different editions of JIRA in relation to these concepts.

Standard Edition: Basic Configuration

In Standard Edition, you have one global Field Configuration and one global Screen Scheme. Any changes you make to the Field Configuration, Screens or Screen Scheme are applicable across all projects.

Professional Edition: Screens Per Project

Professional Edition provides multiple Screen Schemes. Each project has a Screen Scheme. Each Screen Scheme can have different Screens associated with different issue operations. For example, you can have different 'Edit' screens from one project to another. Once you have set up the Screen Schemes, you can reuse the same scheme for multiple projects.

Note that, in Professional Edition, any changes you make to the Field Configuration are applicable across all projects.

Enterprise Edition: Screens and Field Configurations Per Project and Issue Type

JIRA adds further flexibility for Enterprise Edition by providing different Screens and Field Configurations per issue type.

Each project has an Issue Type Screen Scheme. Issue Type Screen Schemes allow you to associate Screen Schemes with issue types. This allows you to specify different Screens for the same operation (e.g. 'Create Issue') in the same project for issues of different types. For example, you could use one screen when creating an issue of type 'Bug', and a different screen when creating an issue of type 'Task'.

Additionally, each project has a Field Configuration Scheme. Field Configuration Schemes allow you to associate Field Configurations with issue types. This allows you to specify different field behaviour for the same field in the same project for issues of different types.