Resin Upgrade to 3.0.9

Installing Jira

Redisn Install

Resin Config.

EPPI Config with 3.0.9

Novum Config with 3.0.9

Jira Install.

Jira Config.

Mail Server Config.

------

Setting up JIRA for your Project.

JIRA is a software development issue tracking tool that appears to be initially something the developer would set, administare and use. However it can just as easily be used by the client of the developer.

All items not mentioned here should be left at the default.

JIRA Setup Step 1 of 3: Application properties Global properties for this install of JIRA. Existing data? If you have already setup JIRA before, you can import your existing data instead of running the setup wizard again.

* Genw orth Financial PPI Issue Tracker Application Title: The application title will be used to 'name' this installation.

* Mode: Private JIRA can operate in two modes: 1. Public - Any user can signup and post issues. 2. Private - Only administrators can create new users.

* Base https://w w w .rsv-test.com:443/atlassian-j URL: This is the base URL of this installation of JIRA. All links created (for emails etc) will be prefixed by this URL.

* Index index path: Enter an absolute directory path where JIRA can store the indexes. If the path does not exist, JIRA will try to create it for you.

Attachment attachments Path: If you would like to allow attachments to issues, enter a directory path where JIRA can store the attachments. If the path does not exist, JIRA will try to create it for you. Backup backups Path: JIRA provides the option to automatically backup your data every 12 hours. We highly recommend this option. If you would like to enable this option please specify a directory for JIRA to store the backups.

License * License Key:

Enter your JIRA license key - either commercial or evaluation. You can generate an evaluation license instantly online

Next>>

Lkjlkjlkj

JIRA Setup Step 3 of 3: Email Notification Setup the email server to be used for email notifications, or turn them off.

Disable Email Notifications

Name: Default SMTP Server The name of this server within JIRA.

From scott.burgess@genw orth.com address: The default address this server will use to send emails from (be sure that this email address is allowed to send mail through the server specified).

Email [JIRA] prefix: A prefix which is prepended to every subject (useful in helping users filter mail).

Server Details Enter either the host name of your SMTP server or the JNDI location of a javax.mail.Session object to use. SMTP Host

Host cin01ssbhmailge.gemail.ge.com Name: To send email notifications via an SMTP server, enter the host name of the SMTP server Username: Optional - if you use authenticated SMTP to send email, enter your username. Password: Optional - as above, enter your password if you use authenticated SMTP. or JNDI Location JNDI Location: To send email notifications via an existing mail session, enter the JNDI location of the javax.mail.Session object.

Finish

First Set up your User Groups.

Defined three user group types:

Testers – Able to open and edit bugs. TIA Developers – Able to work on issues and resolve them. GEFI Developers – As above. Reasons I separated this is I do not know if it is possible later to do time tracking for each dev. group.

Default user groups:

Jira Admins – Able to administer Jira. If you select this does it give all permissions below this such as Developer, Tester etc? Have mailed Jira. Jira Users – default type on creation. It appears that you have to have to belong to this group to be able to login.

The permissions of the actions a particular group can do are defined in the TNT Permissions Scheme.

Set up your users and assign them to groups.

Do this using the User Browser. You will need to add at least your key testers and development component leaders.

These Users will be able to work on all Projects in Jira. I am not sure how yet to define different roles for different projects although this should be possible using different permission schemes.

Now Define a Project.

Key: TNT – this prefixes all bugs references with this suffix. Eg. TNT-1 URL: No URL Lead: Donnchadh O'malley - This is the Lead Developer and it is a project default that they are auo assigned all issues to reassign to coders. However using components below we are able to avoid hat and therefore it makes more sense to have the GEFI UAT leader defined here. Default Assignee: Project Lead Notification Scheme: Default Notification Scheme ( select scheme | edit notifications ) Permission Scheme: TNT Permission Scheme ( select scheme | edit permissions ) - Initially only default Permission schemes will be available so choose that one first and not as here. Issue Security Scheme: None ( select scheme ) Field Layout Schemes: System Default Layout Workflow Scheme: TNT workflow Scheme ( select scheme ) CVS Modules: None ( select modules ) Mail Configuration: Mail notifications from this project will come from the default address ( edit configuration ) Project Category: None ( select category )

Add Components and Component Leads.

Components Add new component, select assignees for components

Components.

Defined as:

Component Development Lead

Area Owner User Id Claims ccallcut Configuration Erik Jacobsen Customer mbadman Document Production rliebenberg Finance mpant Other rliebenberg Policy mbadman Product mbadman Reinsurance rliebenberg Scheme Loader taulakh

Upon creating an issue it is automatically assigned to the appropriate development lead.

You then need to ‘Select’ Assignees as below so that bugs are auto assigned.

Project: TNT CH and DE v.0.1 Key: TNT URL: No URL Lead: Donnchadh O'Malley Default Assignee: Project Lead Notification Scheme: None Permission Scheme: None Issue Security Scheme: None Field Layout Schemes: System Default Layout Workflow Scheme: None CVS Modules: None Project Category: None Select Component Assignee Use this page to select default assignees for newly created issues.

Component Name Component Lead Default Component Assignee

Project Project Default Lead (lead: Claims Claire Callcut Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Claire disabled. Callcut)

Project Project Default Lead (lead: Configuration Erik Jacobsen Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Erik disabled. Jacobsen)

Project Project Default Lead (lead: Customer Mark Badman Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Mark disabled. Badman)

Project Project Default Lead (lead: Document Production Roddi Liebenberg Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Roddi disabled. Liebenberg)

Project Project Default Lead (lead: Finance Manoj Pant Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Manoj disabled. Pant) Other Roddi Liebenberg Project Project Default Lead (lead: Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Roddi disabled. Liebenberg)

Project Project Default Lead (lead: Policy Mark Badman Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Mark disabled. Badman)

Project Project Default Lead (lead: Reinsurance Roddi Liebenberg Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Roddi disabled. Liebenberg)

Project Project Default Lead (lead: Scheme Loader Tony Aulakh Donnchadh O'Malley) Unassigned Component issues are Lead (lead: Tony disabled. Aulakh)

Update

Manage Versions.

Versions Manage versions 02Q 17/Dec/04 02R 16/Dec/04 02S 16/Dec/04 02T 24/Dec/04

Not sure how this works yet!! I assume it influences workflow and resolution in some way….

Global Settings.

Attachments Should be Turned ON Issue Linking – Turn it ON. This enables developers to link duplicate issues or show dependencies between one issue and another.

Mail Servers.

SMTP Mail Servers The table below shows the SMTP mail servers currently configured for this server Name Details Default SMTP From: Edit Server [email protected] Del Prefix: [JIRA] Send a Test Host: Email cin01ssbhmailge.gemail.ge.com

Time Tracking

Time Tracking Time Tracking is currently ON. The number of working hours per day is 7. The number of working days per week is 5. N.B. To change these value deactivate and then reactivate Time Tracking. For the users you wish to be able to log work on issues, ensure that they have the Work On Issues permission in the relevant permission scheme. To deactivate Time Tracking, simply click below.

I turned this on. Not sure what we can use it for yet but it looks useful!

Workflows.

Looks interesting but I haven’t played with it enough to understand how we could leverage its flexibility.

Schemes

Notification.

This seems like a lot of e-mails. You may want to turn some of these off!!

Permission Schemes. You should create a copy of the default scheme and use that as a template for modifying to suit your user groups. Here is the first try config for TNT.

Permission Users / Groups Operations Administer Projects Group (jira- Add Ability to administer a project in JIRA. administrators) (Del) Browse Projects Group (Testers) Add Ability to browse projects and the issues within them. (Del) Group (jira-users) (Del) Create Issues Group (Testers) Add Ability to create issues. (Del) Group (jira-users) (Del) Edit Issues Group (TIA Add Ability to edit issues. developers) (Del) Group (GEFI Developers) (Del) Schedule Issues Group (TIA Add Ability to set or edit an issue's due date. developers) (Del) Group (GEFI Developers) (Del) Move Issues Group (TIA Add Ability to move issues between projects. Note the user (Del) can only move issues to a project he or she has create developers) permission for. Group (GEFI Developers) (Del) Assign Issues Group (TIA Add Ability to assign issues to other people. developers) (Del) Group (GEFI Developers) (Del) Assignable User Group (Testers) Add Users with this permission may be assigned to issues. (Del) Group (GEFI Developers) (Del) Group (TIA developers) (Del) Group (jira-users) (Del) Resolve Issues Group (TIA Add Ability to resolve and reopen issues. This includes the developers) (Del) ability to set a fix version. Group (GEFI Developers) (Del) Close Issues Group (TIA Add Ability to close issues. Often useful where your (Del) developers resolve issues, and a QA department developers) closes them. Group (GEFI Developers) (Del) Modify Reporter Group (TIA Add Ability to modify the reporter when creating or editing an issue. developers) (Del) Group (jira- administrators) (Del) Add Comments Group (Testers) Add Ability to comment on issues. (Del) Group (jira-users) (Del) Delete Issues Group (jira- Add Ability to delete issues, comments and attachments. administrators) (Del) Work On Issues Group (TIA Add Ability to log work done against an issue. Only useful if developers) (Del) Time Tracking is turned on. Group (GEFI Developers) (Del) Link Issues Group (TIA Add Ability to link issues together and create linked issues. developers) (Del) Only useful if issue linking is turned on. Group (GEFI Developers) (Del) Create Attachments Group (Testers) Add Users with this permission may create attachments. (Del) Group (jira-users) (Del) View Version Control Group (TIA Add Ability to view Version Control commit information for developers) (Del) issues. Group (GEFI Developers) (Del) View Voters and Watchers Group (TIA Add Ability to view the voter and watcher list of an issue. developers) (Del) Group (GEFI Developers) (Del) Manage Watcher List Group (jira- Add Ability to manage the watcher list of an issue. administrators) (Del) Set Issue Security Add Ability to set the level of security on an issue so that only people in that security level can see the issue.

Issue Fields.

Custom fields

I have created the following custome fields. Soemare required going forward eg. Country, but some are there as they may be needed for impoarting the old data set. Eg. Old Bug Ref.

Name Type Searcher Default Scope Country Radio Buttons Radio Button Searcher Global (all issues) Edit | Edit Defaults | Del | Edit Options The country where the issue was found Environment Multi Checkboxes Multi Checkbox Searcher Global (all issues) Edit | Edit Defaults | Del | Edit Options where issue seen Old Bug Doc Text Field (< 255 characters) Free Text Searcher Global (all issues) Edit | Edit Defaults | Del Ref Name Old Master Number Field Number Searcher Global (all issues) Edit | Edit Defaults | Del Error Log number Old Stream Number Field Number Searcher Global (all issues) Edit | Edit Defaults | Del Error Log Number Work Stream Select List Select List Searcher Global (all issues) Edit | Edit Defaults | Del | Edit Options Field Layout System.

This is a first try.

Name Order Operations

Summary Required Edit Work Stream Edit | Show

Issue Type Required Edit Security Edit | Hide | Required Level

Priority Required Edit | Hide | Optional Due Date Edit | Hide | Required

Country Required Edit | Hide | Optional The country where the issue was found Environment Edit | Hide | Optional where issue seen Required Environment Edit | Show For example operating system, software platform and/or hardware specifications (include as appropriate for the issue).

Assign To Required Edit | Hide

It gives a bug creation screen like this.

Project: TNT CH and DE Issue Type: Bug * Summary:

* Priority: Trivial Due Date: * Country: CH DE * Environment Model Office DEV where issue seen: Model Office Prod UAT Training Migration 1 Migration Prod Sand Box Production

* Unknow n Claims Component/s: Document Production Finance Policy Old Master Error Log number: Old Stream Error Log Number: Affects Unknow n Unreleased Versions Version/s: - 02Q - 02R - 02S Fix Version/s: Unknow n Unreleased Versions - 02Q - 02R - 02S

* Assign To: - Automatic -

Reporter: domalley Description:

Old Bug Doc Ref Name: Attachment: The maximum file upload size is 5.00 Mb. Please zip files larger than this. Original Estimate: An estimate of how much work remains until this issue will be resolved. The format of this is ' *w *d *h *m ' (representing weeks, days, hours and minutes - where * can be any number) Examples: 4d, 5h 30m, 60m and 3w.

Navigator Columns.

A first try.

Re-order Columns

The table below contains sample data to show you an example of what your Issue Navigator will look like using the selected columns. Use and to rearrange the column order, and to remove a column from your list.

T Key Old Ref Old Stream Ref Summary Components Assignee Reporter Pr Status Res Created (The old ref number in the master error log) (The old ref in the stream log)

TNT-11 for clair Claims Claire Calcut Raj Nair Open UNRESOLVED 10/Dec/04 !st Test TNT-10 Bug Policy mark badman Raj Nair Open UNRESOLVED 10/Dec/04 entered

IMPORTING DATA FROM EXCEL.

There is a help page at : http://www.atlassian.com/software/jira/docs/latest/csv_import.html

The example excel file it gives you there is almost correct but not quite! If a parse exception occurs it is still very likely that the import has occurred. Eg. Incorrect date format will cause an exception but records will be imported with all non-parsed dates set to the time and date of import

> 1) Is it possible to add a new field/radio button/ drop down > list at a later time to the bug submission form as > requirements change?

Yes, it is indeed possible to add a custom field at any time.

> 2) If I do that and then use that parameter as reporting or > filter item then what happens to the old database records > that do not have that parameter attached. Are they simply not > reported at all or are they reported as exceptions or unkowns?

Yes, correct they would simply not be reported.

> 3) Similarly can I add a new status such as 'resolved for > retest' type at a later time?

Not exactly. To add a new status you will need to create a new workflow (e.g. by copying the current workflow) and then edit this copy as necessary and migrate all the issues to this workflow. > 4) When I export the DB to XML does it export 'everything' > including the db contents and the projects complete > configuration (defined workflows, permissions, form > layouts....) including user accounts?

This exports everything in the database. Please note that the attachments themselves are not exported as they are kept on disc outside of the database. You can read more about exporting here: http://www.atlassian.com/software/jira/docs/latest/backup_data.html