JIRA is the business's issue tracking software that we have successfully upgraded from version 7.1 to 7.3. The upgrade contains a Wiki-style Rich Text Editor for use in the Description and Comments. As well as the ability to format text, the editor can be used to insert:
- Code blocks & Panels
- User @ Mentions
JIRA 7.3 also introduces several other minor changes to the user interface to improve usability, convenience and efficiency.
The upgrade took place over the weekend beginning 28/7 and JIRA was successfully deployed on 31/7.
The project was completed 18 days under budget and deployment to LIVE was completed 28 days early
- Upgrade JIRA from version 7.1 to 7.3
- Upgrade JIRA database from Oracle 12.1.to 12.2
- Review documentation (README’s) for JIRA version 7.3 and decide what new functionalities to give to the business
- Integration testing for the latest version
- User acceptance testing for the latest version
- Upgrade LIVE to latest version
Objectives and Deliverables
To complete the JIRA upgrade from version 7.1 to 7.3 with as little disruption to service as possible
|D1.1||Upgrade version of JIRA from 7.1 to 7.3 on DEV, TEST and LIVE||M||Achieved|
|D1.2||Refresh TEST and DEV from LIVE||S||Achieved|
To upgrade JIRA databases from version 12.1 to 12.2
|D2.1||Upgrade 12.1 to 12.2 on DEV, TEST and LIVE||S||Achieved|
Complete full tests of the upgraded service
|D3.1||Review documentation from JIRA 7.1 to 7.3||M||Achieved|
|D3.2||Identify what is new and what should be given out to the business||M||Achieved|
|D3.3||Thoroughly test new features in 7.3||M||Achieved|
|D3.4||Complete UATs for version 7.3 of JIRA||M||Achieved|
Analysis of Resource Usage:
Staff Usage Estimate: 40.0 days
Staff Usage Actual: 22.0 days
Staff Usage Variance: -45%
|Planned Date||Actual Date|
Explanation for variance
Resources became available, so team members were keen to push milestones forward so the work could be completed before people went on annual leave. No issues were raised following deployment to LIVE so no additional work needed to be put in that may have caused the milestones to be pushed back. Sign offs were attained quickly and with ease as team members were comfortable with the tasks and associated milestones.
Key Learning Points
- Should have had an indication of what method we would use to lock down JIRA for specific users before the upgrade, and tested this
- Getting round issues was handled well as the upgrade is annual and had been done before
- All team members had a good sense of direction and knew which tasks they had to complete. Communication was good - with everyone attending weekly meetings where possible and communicating through HipChat and email.
To think about for the next annual upgrade:
- The refresh of the database copies licensing from LIVE into TEST, so the upgraded version had the wrong license.
- Locking JIRA down to certain IP address caused small issues - see Closed JIRA log