JIRA 101

1. Download the appropriate JIRA Windows Installer (.exe) file (which matches the 'bit' version of your Windows operating system) from the JIRA download page.
2. Run the '.exe' file, choose an installation directory, a home directory and a port ('8080' will do). We recommend that you choose to 'Run JIRA as a service'.
3. To access JIRA, go to your web browser and type this address: http://localhost:8080. Windows 'Start' menu shortcuts will also be added which you can also use to start and stop JIRA.
4. Follow the Setup Wizard. This will guide you through the process of setting up your JIRA server, creating an Administrator user and (optionally) setting up email.

For more help on the technical procedures in this section, see the JIRA Installation Guide.

If you need assistance, please create a support ticket.

Before using JIRA as a production system, ensure that you have configured JIRA to use a supported database other than JIRA's internal HSQL database (which is provided for evaluation purposes only). Please see the documentation for details.

1. Download the appropriate Linux Installer (.bin) file (which matches the 'bit' version of your Linux operating system) from the JIRA download page.
2. Open a console as the 'root' user (e.g. open a shell and enter the command 'su root').
3. Execute the '.bin' file, choose an installation directory, a home directory and a port ('8080' will do). (If you execute the '.bin' file with 'root' user privileges, JIRA will be installed as a service and will run under a dedicated 'jira' user account.)
4. To access JIRA, go to your web browser and type this address: http://localhost:8080.
5. Follow the Setup Wizard. This will guide you through the process of setting up your JIRA server, creating an Administrator user and (optionally) setting up email.

For more help on the technical procedures in this section, see the JIRA Installation Guide.

If you need assistance, please create a support ticket.

Before using JIRA as a production system, ensure that you have configured JIRA to use a supported database other than JIRA's internal HSQL database (which is provided for evaluation purposes only). Please see the documentation for details.

JIRA running on Mac OS X is supported for evaluation purposes only.

1. Download the JIRA Standalone (tar.gz) file from the JIRA download page and extract it.
2. Edit the jira-application.properties file in the JIRA Installation Directory, add a 'jira.home' property and set it to your desired location for the JIRA home directory. Please use forward-slashes ("/"), not back-slashes ("\").
3. Run bin/start-jira.sh to start JIRA.
4. To access JIRA, go to your web browser and type this address: http://localhost:8080.
5. Follow the Setup Wizard. This will guide you through the process of setting up your JIRA server, creating an Administrator user and (optionally) setting up email.

For more help on the technical procedures in this section, see the JIRA Installation Guide.

If you need assistance, please create a support ticket.

• Use the Quick Search box in the top of your screen to quickly search JIRA. You can type an issue key (e.g. TEST-1234) to jump directly to an issue, or use syntax like my open issues to immediately return all issues which are assigned to you and haven't yet been resolved.

1. Choose Issues > Search for Issues on the top navigation bar to display JIRA's searching and filtering panel.
2. Select the Project, Issue Type, or any other issue attributes of interest. You can also perform comprehensive text searches when using the  basic search.

1. Click Issues > Search for Issues on the top navigation bar, then click Switch to Advanced to display the JQL (JIRA Query Language) panel.
2. Type your query (e.g. 'project=TEST') and press Enter/Return on your keyboard.

1. View your search results (see 'Searching' above) in the Issue Navigator.
2. Click the 'Views' menu and select the 'Charts' option.
3. Choose your preferred type of chart, and enter any required configuration details. For more details, please see the documentation.

1. Click 'Projects' in the top navigation bar.
2. Select the project you are interested in.
3. Click 'Reports' at the right of the screen and select the report of interest.
4. Enter any required configuration details, then click 'Next' to display your report (e.g. Workload Pie Chart Report).

1. View your search results (see 'Searching' above) in the Issue Navigator.
2. Click the 'Views' menu and select 'Word', 'Excel', or your preferred format. For more details, please see the documentation.

You may want to create a sample project named 'Purchase Orders', in which to perform the tasks described in this section. For instructions, please see 'Creating a Project' (above).

The Issue Type is one of the first things a user must choose when they create an issue.
Depending on how your organisation is using JIRA, you might want to add a new Issue Type.
For example, if you are using JIRA to track purchase orders, the default Issue Types ('Bug', 'Improvement', 'New Feature', 'Task') might not be relevant. So you might want to add a new Issue Type called 'Order'.

To add a new Issue Type called 'Order', and associate it with a project called 'Purchase Orders':

1. Choose Administration at the top right of your screen.
2. Select 'Issues' > 'Issue Types'.
3. In the 'Add New Issue Type' form, in the 'Name' field, type 'Order. In the 'Description' field, type 'A purchase order'. Then click the 'Add' button'. (For more about adding Issue Types, and icons, please see the documentation.)
4. Click the 'Issue Types Scheme' tab at the top of the 'Manage Issue Types' screen.
5. In the 'Add New Issue Type Scheme' form, in the 'Name' field, type 'Purchase Order Issue Type Scheme'. Then click the 'Add' button'. (For more about Issue Type Schemes, please see the documentation.)
6. In the 'Available Issue Types' list, click the Issue Type called 'Order' and drag it into the 'Issue Types for Current Scheme' list. Then click the 'Save' button.
7. Click 'Projects' in the left navigation column. Then in the 'Name' column, click 'Purchase Orders'. The project details will be displayed.
8. Click the 'Select' link next to the 'Issue Type Scheme' field, select 'Purchase Order Issue Type Scheme' and click the 'Associate' button.

To test what you have done, create an issue in the 'Purchase Orders' project. The only available Issue Type should be 'Order'.

Depending on how your organisation is using JIRA, you might want to add a purpose-built screen that will be displayed for particular types of issues, or for particular projects or workflows.
For example, if you are using JIRA to track purchase orders, some of the normal issue fields (e.g. 'Affects Version', 'Fix Version', 'Environment') might not be relevant. So you might want to create a simplified screen that omits these fields.

To add a new Screen called 'Purchase Order Screen', and associate it with a project called 'Purchase Orders':

1. Choose Administration at the top right of your screen.
2. Select 'Issues' > 'Screens'.
3. Click the 'Copy' link next to 'Default Screen'.
4. In the 'Name' field, type 'Purchase Order Screen'. Then click the 'Copy' button'. (For more about Screens, please see the documentation.)
5. Click the 'Configure' link next to 'Purchase Order Screen'.
6. Tick the 'Remove' box for the following fields: 'Affects Version', 'Fix Version', 'Environment'. Then click the 'Remove' button.
7. Click 'Screen Schemes' in the left navigation column (under 'Issue Fields').
8. In the 'Name' field, type 'Purchase Order Screen Scheme'. In the 'Default Screen' field, select 'Purchase Order Screen'. Then click the 'Add' button'. (For more about Screen Schemes, please see the documentation.)
9. Click 'Issue Type Screen Schemes' in the left navigation column (under 'Issue Fields').
10. In the 'Name' field, type 'Purchase Order Issue Type Screen Scheme'. In the 'Screen Scheme' field, select 'Purchase Order Screen Scheme'. Then click the 'Add' button'. (For more about Issue Type Screen Schemes, please see the documentation.)
11. Click 'Projects' in the left navigation column. Then in the 'Name' column, click 'Purchase Orders'. The project details will be displayed.
12. Click the 'Select' link next to the 'Issue Type Screen Scheme' field, select 'Purchase Order Issue Type Screen Scheme' and click the 'Associate' button.

To test what you have done, view an issue in the 'Purchase Orders' project. You shouldn't see the 'Affects Version', 'Fix Version' or 'Environment' fields.

Depending on how your organisation is using JIRA, you might need to add a 'custom' field that will be displayed for particular types of issues, or for particular projects.
For example, if you are using JIRA to track purchase orders, you might create a custom field called 'Supplier'.

To create a new custom field called 'Supplier' and put it on the 'Purchase Order Screen':

1. Choose Administration at the top right of your screen.
2. Select 'Issues' > 'Fields' > 'Custom Fields'.
3. Click 'Add Custom Field'.
4. On the 'Create Custom Field - Step 1' screen, in the 'Field Type' field, choose 'Select List'. Then click the 'Next' button.
5. On the 'Create Custom Field - Step 2' screen:
   
   1. in the 'Name' field, type 'Supplier'.
   2. in the 'Description' field, type 'Choose the supplier for this Purchase Order'.
   3. under 'Choose applicable issue types' select 'Order'. Then click the 'Finish' button.
6. On the 'Associate field Order to screens' screen, tick the check-box for 'Purchase Order Screen'. Then click the 'Update' button.
7. On the 'View Custom Fields' screen, click the 'Configure' link next to 'Supplier'. Then click 'Edit Options'.
8. Add three options: 'ABC Pty Ltd', 'ACME Pty Ltd', 'XYZ Pty Ltd'. Choose 'ACME Pty Ltd' as the default. Then click the 'Done' button.

To test what you have done, create an issue in the 'Purchase Orders' project. You should see a field called 'Supplier' that has a drop-down box containing your three options.

Depending on how your organisation is using JIRA, you might need to add a new 'Status' , i.e. a new step in the issue 'workflow'.
For example, if you are using JIRA to track purchase orders, you might add a new Status called 'Purchase Approved' .

To add a new Status called 'Purchase Approved', and create a new workflow that has an extra step between 'Open' and 'In Progress':

1. Choose Administration at the top right of your screen.
2. Click 'Statuses' in the left navigation column (under 'Issue Settings').
3. In the 'Name' field, type 'Purchase Approved'. Then click the 'Add' button'. (For more about adding Statuses, and icons, please see the documentation.)
4. Click 'Workflows' in the left navigation column.
5. Click the 'Copy' link next to 'jira (Read-only System Workflow)'.
6. In the 'Workflow Name' field, type 'Purchase Order Workflow'. Then click the 'Copy' button'. (For more about Workflow, please see the documentation.)
7. Click the 'Steps' link next to 'Purchase Order Workflow'.
8. In the 'Add New Step' form:
   
   1. in the 'Name' field, type 'Purchase Approved'.
   2. in the 'Linked Status' field, select 'Purchase Approved'.
   3. click the 'Add' button.
9. Click the 'Add Transition' link next to 'Open':
   
   1. in the 'Name' field, type 'Approve Purchase'.
   2. in the 'Destination Step' field, select 'Purchase Approved'.
   3. click the 'Add' button.
10. Click the 'Add Transition' link next to 'Purchase Approved':
    
    1. in the 'Name' field, type 'Start Progress'.
    2. in the 'Destination Step' field, select 'In Progress'.
    3. click the 'Add' button.
11. Click the 'Delete Transitions' link next to 'Open'. Select 'Start Progress' and click the 'Delete' button.
12. Click 'Workflow Schemes' in the left navigation column (under 'Schemes'). Then click 'Add Workflow Scheme'.
13. In the 'Name' field, type 'Purchase Order Workflow Scheme'. In the 'Default Screen' field, select 'Purchase Order Screen'. Then click the 'Add' button'. (For more about Workflow Schemes, please see the documentation.)
14. Click the 'Workflows' link next to 'Purchase Order Workflow Scheme', click 'Assign Workflow' and select 'Purchase Order Workflow'. Then click the 'Add' button.
15. Click 'Projects' in the left navigation column. Then in the 'Name' column, click 'Purchase Orders'. The project details will be displayed.
16. Click the 'Select' link next to the 'Workflow Scheme' field, select 'Purchase Order Workflow Scheme' and click the 'Associate' button.

To test what you have done, create an issue in the 'Purchase Orders' project. After you save the issue, the left column should contain a link called 'Approve Purchase', but not a link called 'Start Progress'.

Note: you may also want to watch the video on customising JIRA Workflow.

A Permission scheme allows you to grant people 'permission' to work on issues in a project. The new project that you created previously is using JIRA's Default Permission Scheme. If you end up creating lots of projects, you might need to grant different people permission to work on different projects.
For example, if your organisation requires all software development issues to be tested by a Quality Assurance person before being closed, you could create a permission scheme called 'Software Development Permission Scheme' in which you assign the 'Close Issue' permission to the appropriate people. You would then associate your new permission scheme with all your software development projects.
There are a number of ways to do this, depending on your requirements:

• Project roles enable you to associate different people with particular functions, for particular projects.
• Groups enable you to associate the same people with a particular function, for all projects that use this permission scheme.

To add a new permission scheme called 'Software Development Permission Scheme', and a project role called 'Quality Assurance':

1. Create a project role called 'Quality Assurance':
   1. Choose Administration at the top right of your screen.
   2. Select 'Users' > 'Roles' from the top menu.
   3. In the 'Name' field, type 'Quality Assurance'. Then click the 'Add Project Role' button.
2. Create a permission scheme called 'Software Development Permission Scheme', in which you assign the 'Close Issue' permission to the 'Quality Assurance' project role:
   1. Select 'Issues' > 'Permission Schemes' from the top menu.
   2. Click the 'Copy' link next to 'Default Permission Scheme'. A new permission scheme called 'Copy of Default Permission Scheme' will be created.
   3. Click the 'Edit' link next to 'Copy of Default Permission Scheme'. On the 'Edit' screen,
      1. change the 'Name' to 'Software Development Permission Scheme'
      2. change the 'Description' to 'Permission scheme for software development projects'. Then click the 'Update' button.
   4. Click the 'Permissions' link next to 'Copy of Default Permission Scheme'. On the 'Edit Permissions' screen,
      1. for the 'Close Issues' permission, click the 'Delete' link next to 'Project Role (Developers)'.
      2. for the 'Close Issues' permission, click the 'Add' link. Click 'Project Role' and choose 'Quality Assurance'. Then click the 'Add' button.
3. Associate the 'Software Development Permission Scheme' with all your software development projects. Do the following for each relevant project:
   1. Click 'Projects' and select the project of interest. The project details will be displayed.
   2. Click the name of the project's current Permission Scheme, then select 'Software Development Workflow Scheme' and click the 'Associate' button.
4. For each software development project, add the appropriate people to the 'Quality Assurance' project role:
   1. Click 'Projects' and select the project of interest. The project details will be displayed.
   2. Click 'View Project Roles' to display the 'People' screen
   3. Select the 'Edit' link next to 'Quality Assurance' and add the appropriate people.

Or, to add a new permission scheme called 'Software Development Permission Scheme', and a group called 'quality-assurance':

1. Create a group called 'quality-assurance', and add the appropriate people to it.
   1. Choose Administration at the top right of your screen.
   2. Select 'Users' > 'Groups' from the top menu.
   3. In the 'Name' field at the bottom of the page, type 'quality-assurance'. Then click the 'Add Group' button.
2. Create a permission scheme called 'Software Development Permission Scheme', in which you assign the 'Close Issue' permission to the 'quality-assurance' group.
   1. Select 'Issues' > 'Permission Schemes' from the top menu.
   2. Click the 'Copy' link next to 'Default Permission Scheme'. A new permission scheme called 'Copy of Default Permission Scheme' will be created.
   3. Click the 'Edit' link next to 'Copy of Default Permission Scheme'. On the 'Edit' screen,
      1. change the 'Name' to 'Software Development Permission Scheme'
      2. change the 'Description' to 'Permission scheme for software development projects'. Then click the 'Update' button.
   4. Click the 'Permissions' link next to 'Copy of Default Permission Scheme'. On the 'Edit Permissions' screen,
      1. for the 'Close Issues' permission, click the 'Delete' link next to 'Project Role (Developers)'.
      2. for the 'Close Issues' permission, click the 'Add' link. Click 'Group' and choose 'quality-assurance'. Then click the 'Add' button.
3. Associate the 'Software Development Permission Scheme' with all your software development projects. Do the following for each relevant project:
   1. Click 'Projects' and select the project of interest. The project details will be displayed.
   2. Click the name of the project's current Permission Scheme, then select 'Software Development Workflow Scheme' and click the 'Associate' button.