IT Professionals,
Our Jira instance will be moving to Jira Cloud by the end of the summer. There will be preparation work February to May, test migrations in May, and the production migration in July or August.
On Jira Cloud, there will be two instances:
- Jira Software: for project planning and Agile Boards
- Jira Service Management: for projects that are used as ticketing system
Jira Service Management will not replace the ServiceNow service management system. Jira Service Management is recommended for those who are already utilizing Jira for software development and need additional ticketing software inside their development workflow.
Jira project owners are being contacted on Thursday, February 9, with the message below.
If you have questions, please contact jcu@iu.edu.
–IT Community Partnerships on behalf of Atlassian migration team
~~~~~ Text of directing mailing ~~~~~
Subject: Changes coming to Jira
Jira project owners, today we are sharing some exciting news. We are moving our Jira instance from our on-prem offering to Jira Cloud. This will provide new features and the latest versions of the software. Our current platform will be split into two instances of Jira in the Cloud. The first instance will be Jira Software which is the product we have today. This will be used for project planning and Agile Boards. The second instance will be Jira Service Management. This instance will be used for projects that are used as a ticketing system.
Why are we doing this? First, our current on-prem product, Jira Server, will reach end of life on February 2, 2024. Second, splitting our Jira instance into Jira Software and Jira Service Management helps control costs. The unlimited license we have enjoyed since originally deploying Jira 18 years ago is going away. This necessitates moving ticketing to Jira Service Management. This migration will give us a more robust and cost effective ticketing solution in Jira.
General timeline
- The project kickoff took place internally on January 17.
- From February to May, there will be internal work setting up the Cloud space and cleaning up our existing environment in preparation for practice migrations. Questions about individual setups will be targeted to project owners.
- Starting in May, we plan to start test migrations. These will last throughout the summer. Customers will be asked to verify their projects and test any integrations they may have set up.
- The final Production migration will be late in July or early August.
Additional communications will be happening throughout the upgrade lifecycle. Questions can be sent to jcu@iu.edu.
Signed,
Atlassian migration team