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 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 Issue Constant Translatio.. 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

Issue Constant Translations

PDF

Further extending JIRA as an internationalisable issue manager, it is possible to specify a translated name and description for each issue constant - i.e all Issue Type, Status, Resolution and Priority fields.

This functionality allows the administrator to specify an issue constant translation set for each available locale - providing each user with a more complete translation in their own chosen language. The translated issue constant names and descriptions appear throughout JIRA; in reports, portlets and all issue views.

Issue Constant Translation

Each issue constant can be configured to have a translation set for each available locale. The default issue constant name and description are displayed if no translation has been configured.

The issue constant translation operation is accessed through the Translate link located on each issue constant management screen.
The issue constant translation screen displays the translation set for the currently selected locale. In order to view/update a translation set for a specific locale, select the required locale from the list at the top of the screen and click the View button.
The currently selected locale is displayed above the translation set table.
A translated name and description set can be specified for each type of issue constant. Once all translations have been entered, the translation set can be saved by clicking the Update button at the bottom of the translation table.
The process can be repeated for the all types of issue constants - i.e. Issue Type, Status, Resolution and Priority fields.
The translated issue constant name and description will be displayed throughout JIRA; in reports, portlets and all issue views.

Note

The default issue constant name and description are displayed if a translation has not been specified.