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 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) Introduction Step 1: Ensure no Enterpr.. Create an XML backup Delete license key Import and reenter licens.. 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

Downgrading from JIRA Enterprise to JIRA Professional

PDF

Introduction

Occasionally people start out evaluating JIRA Enterprise, and then decide that they will not need the extra features, and switch to JIRA Professional.

While JIRA can automatically upgrade data from Professional to Enterprise by adding the additional tables, it cannot automatically do the opposite. Downgrading data from Enterprise to Professional requires some manual intervention, described in this document.

Step 1: Ensure no Enterprise features are used

Log into JIRA as a user with permission jira-administrator. In the 'Administration' section, check that for each project:

Issue Security Scheme is set to None.
Field Configuration Scheme is set to System Default Field Configuration
Issue Type Screen Scheme is set to Default Issue Type Screen Scheme.
Workflow Scheme is set to None
Project Category is set to None

Also ensure that in the permission schemes and notification schemes, only 'groups' or 'project roles' are specified (i.e., no 'Current Reporter', 'Single User', 'Project Lead' or 'Current Assignee').

Create an XML backup

In the 'Administration' section, click Backup Data to XML and create an uncompressed XML backup.

Delete license key

Open the saved XML dump, locate the section containing OSPropertyString tags, and specifically the lines recording the license key, for example:

<OSPropertyString id="10012"
  value="QmSSppmNrnRemqoaaaXONrrNRMQONpqqqTsUwTXvuuSVoreeeemsqostsnmsunUUnmsqostsnmsqnUU9kabmbkaakq"/>
<OSPropertyString id="10013"
  value="NNORRIhehJHuopbJHahmlCIOpNUquvoaWtvMnSqAcaussss2KqaVqLs<18T3yRGL9AaQ12KlGXNCsNU9K7uYRPqKB<K"/>

Replace the values within the double quotes with:

<OSPropertyString id="10012"
value="mNxwOOpqNMnqnNRonTWRpNqOoORQnNNPsSswxSTtStvTTMuXUWuxTQxtxXSswqtUUnmsurpmqmmmmmUUnmsurpmqmmmmmUUGiXZbeliaboWbumfobaWifZbkpb"/>
<OSPropertyString id="10013"
value="OqPNWKIpAHlnPweAodiBiOpuPNPUBMMxPGwgcFPehrlPwOmi2K6aWBoeqgwqTRPQU3n23f2KYGb5TyaE8G9YQv1gBNKT"/>

(Make sure the original id attributes remain the same - "10012" and "10013" are just examples)

Import and reenter license key

Now shut down the JIRA Enterprise, and start up a JIRA Professional instance. Import the XML saved in the last step.

In the footer, JIRA will claim that it has an expired license. Log in as an administrator and enter your Professional license key.