Background
This project aims to deliver an annual upgrade of the business’ issue tracking software, JIRA. It will involve upgrading from JIRA version 7.13 to an updated version selected by the project team (8.5.5).
The project intends to keep software up-to-date and ensure it remains supported. This year's project will not involve database upgrades or any major development tasks.
Scope
- Upgrade JIRA from version 7.13 to the latest available Enterprise Release 8.5.5 to avoid running a version of the software beyond Atlassian’s “end of life"(28th November, 2020).
- Review documentation (README’s) for new JIRA version and decide what features will/won’t be included in the upgrade.
- User Acceptance Testing for the updated version.
- Upgrading LIVE to the updated version.
Out of scope
Oracle Database upgrades will not be required this year as the latest version (12.2) is already in place.
Objectives and Deliverables
Deliverables are ranked using the MoSCoW prioritisation method. (M =Must Have; S = Should Have; C = Could Have; W = Want)
|
Priority |
O1. Complete the JIRA upgrade from version v7.13 to new version with minimal disruption to the current service
|
|
M |
D1.1 Refresh DEV, TEST from LIVE servers |
S |
D1.2 Upgrade JIRA on DEV, TEST and LIVE servers |
M |
O2. Complete full tests of the upgraded service
|
|
M |
D2.1 Review JIRA upgrade documentation and select features to keep or discard
|
|
M |
D2.2 Complete Integration tests of new JIRA features
|
|
M |
D2.3 Complete User Acceptance Testing for new JIRA version
|
|
M |
Benefits
- Users will benefit from new features in updated JIRA version. This will include bug fixes in previous releases, improved functionality and better user experience.
- Version 8.5 will introduce key features like issue archiving, batching emails and Jira Server Mobile app.
- By doing annual upgrades, we ensure future upgrade projects have a reduced scope and budget.
- Research and Key Learning Points can be adopted and reused in future upgrades.
- Improved security and reliability of the system.
Success Criteria
- The software maintains its current working condition and causes minimal disruption during the upgrade.
- Database encryption/security is maintained with no data or data quality is lost.
- Research and Key Learning Points can be adopted and reused in future upgrades.
- Improved security and reliability of the system.
Project Milestones